high CVSS 7.8

CVE-2024-50269·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: usb: musb: sunxi: Fix accessing an released usb phy Commit 6ed05c68cbca ("usb: musb: sunxi: Explicitly release USB PHY on exit") will cause that usb phy @glue->xceiv is accessed after released. 1) register platform driver @sunxi_musb_driver // get the usb phy @glue->xceiv sunxi_musb_probe() -> devm_usb_get_phy(). 2) register and unregister platform driver @musb_driver musb_probe() -> sunxi_musb_init() use the phy here //the phy is released here musb_remove() -> sunxi_musb_exit() -> devm_usb_put_phy() 3) register @musb_driver again musb_probe() -> sunxi_musb_init() use the phy here but the phy has been released at 2). ... Fixed by reverting the commit, namely, removing devm_usb_put_phy() from sunxi_musb_exit().

Severity
high
Software
Kernel
Fixed in
6.11.8
Published
2024-11-19

Affected versions

From: 6.7

Until: 6.11.8

Fixed in: 6.11.8

How to fix this CVE

Update your Linux kernel to version 6.11.8 or later to resolve a use-after-free vulnerability in the Sunxi USB PHY driver. This flaw occurs when the USB PHY is accessed after being prematurely released during driver re-initialization, potentially causing system instability or crashes. Apply the kernel update immediately and reboot your system to ensure the patch is active.

sudo dnf update kernel kernel-devel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check your kernel version: uname -r | awk -F. '{print $1"."$2"."$3}' and compare against 6.11.8
  2. Verify if Sunxi USB PHY support is compiled: grep -i sunxi /boot/config-$(uname -r) or lsmod | grep -i sunxi
  3. Check kernel logs for PHY-related errors: journalctl -k | grep -i 'phy\|musb\|usb' | tail -50
  4. Confirm patch application by checking: cat /proc/version and verify kernel build is >= 6.11.8

FAQ

What is CVE-2024-50269?

CVE-2024-50269 is a use-after-free vulnerability in the Linux kernel's Sunxi USB PHY driver where the PHY object is incorrectly released and then accessed again during driver re-initialization cycles, potentially causing kernel panic or data corruption.

Is CVE-2024-50269 being actively exploited?

No, CVE-2024-50269 is not listed on CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available. However, the high CVSS score (7.8) warrants timely patching.

What versions of Kernel are affected by CVE-2024-50269?

Kernel versions 6.7 through 6.11.7 are affected. The vulnerability is resolved in kernel 6.11.8 and later.

How do I check if my server is vulnerable to CVE-2024-50269?

Run 'uname -r' and check if the version is between 6.7 and 6.11.7. If yes, your system is vulnerable. Also verify Sunxi USB support is enabled with 'grep CONFIG_USB_MUSB_SUNXI /boot/config-$(uname -r)'.

Does Defensia detect CVE-2024-50269?

Yes — Defensia's CVE advisory scanner compares installed kernel package versions against the NVD database. If Linux kernel is installed on a monitored server, CVE-2024-50269 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-50269. Free for 1 server.

Get started free