Look up another CVE · open CVE-2024-50057 in the interactive tracker
CVE-2024-50057
usb: typec: tipd: Free IRQ only if it was requested before
Published 2024-10-21 (24 months ago) by the Linux kernel CNA. Subsystem drivers/usb. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2024-50057 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.11.4-1 | Update the kernel and reboot. Fixed in 6.11.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.11.4-1 | Update the kernel and reboot. Fixed in 6.11.4-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.11.4-1 | Update the kernel and reboot. Fixed in 6.11.4-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/usb/typec/tipd/core.c
- What this is
- USB TYPEC CLASSMAINTAINERS section matched on drivers/usb/typec/ · linux-usb@vger.kernel.org · Maintained
- Kernel module
- none to look for. The file would have gone into tps6598x, and Debian does not compile it into that module, so finding tps6598x in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_OF|CONFIG_PCI|CONFIG_TYPEC|CONFIG_TYPEC_TPS6598X|CONFIG_USB|CONFIG_USB_GADGET|CONFIG_USB_PHY|CONFIG_USB_SUPPORT' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_OF, CONFIG_PCI, CONFIG_TYPEC, CONFIG_TYPEC_TPS6598X, CONFIG_USB, CONFIG_USB_GADGET, CONFIG_USB_PHY, CONFIG_USB_SUPPORT
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2024-10-21 (24 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.21%, higher than 10.7% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/usb
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.15 | 6.6.57 | b72bf5cade51 |
| 4.15 | 6.11.4 | 4d4b23c11954 |
| 4.15 | 6.12 | db63d9868f7f |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2024-50057, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.