Linux · Linux kernel · CWE-908 · published 2024-11-19
CVE-2024-50302Linux Kernel Use of Uninitialized Resource Vulnerability
This week Known exploited in the wild.
CVE-2024-50302 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2025-03-04. EPSS estimates a 0.8% chance of exploitation in the next 30 days, higher than 57% of all CVEs. This Linux kernel vulnerability: CVSS 5.5 (v3.1). Patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux; Red Hat Enterprise Linux still has unfixed releases. US federal agencies must remediate by 2025-03-25. Patch this week.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (federal due date 2025-03-25)
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | linux | Fixed in 6.11.9-1 |
| 12 bookworm | linux | Fixed in 6.1.119-1 | |
| Ubuntu (+143 more packages) | 24.04 LTS | linux | Fixed in 6.8.0-57.59 |
| 22.04 LTS | linux | Fixed in 5.15.0-133.144 | |
| 20.04 LTS | linux | Fixed in 5.4.0-208.228 | |
| Red Hat Enterprise Linux | RHEL 10 | kernel | Not affected |
| RHEL 9 | kernel | Fixed in 5.14.0-503.31.1.el9_5 RHSA-2025:2627 | |
| RHEL 9 | kernel-rt | No fix yet | |
| RHEL 8 | kernel | Fixed in 4.18.0-553.44.1.el8_10 RHSA-2025:2473 | |
| RHEL 8 | kernel-rt | Fixed in 4.18.0-553.44.1.rt7.385.el8_10 RHSA-2025:2474 |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Operating systemLinux kernel
Use of Uninitialized ResourceCVE-2024-50302
Why: Known exploited in the wild.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | Yes, added 2025-03-04 | CISA KEV |
| Ransomware use | Unknown | CISA KEV |
| EPSS (30-day exploitation probability) | 0.8% (58th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.5 (v3.1)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | active | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Weakness: CWE-908: Use of Uninitialized Resource
More from this vendor: all Linux vulnerabilities · recent KEV additions
Affected versions (from the CVE record)#
- Linux Linux
27ce405039bfe6d3f4143415c638f56a3df77dcato beforee7ea60184e1e88a3c9e437b3265cbb6439aa7e26(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato before3f9e88f2672c4635960570ee9741778d4135ecf5(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato befored7dc68d82ab3fcfc3f65322465da3d7031d4ab46(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato before05ade5d4337867929e7ef664e7ac8e0c734f1aaf(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato before1884ab3d22536a5c14b17c78c2ce76d1734e8b0b(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato before9d9f5c75c0c7f31766ec27d90f7a6ac673193191(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato before492015e6249fbcd42138b49de3c588d826dd9648(affected)27ce405039bfe6d3f4143415c638f56a3df77dcato before177f25d1292c7e16e1199b39c85480f7f8815552(affected)b2b6cadad699d44a8a5b2a60f3d960e00d6fb3b7(affected)fe6c9b48ebc920ff21c10c50ab2729440c734254(affected)3.10.16to before3.11(affected)3.11.5to before3.12(affected)
- Linux Linux
3.12(affected)0to before3.12(unaffected)4.19.324through4.19.*(unaffected)5.4.286through5.4.*(unaffected)5.10.230through5.10.*(unaffected)5.15.172through5.15.*(unaffected)6.1.117through6.1.*(unaffected)6.6.61through6.6.*(unaffected)6.11.8through6.11.*(unaffected)6.12through*(unaffected)
Description (from the CVE record)#
In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.
Quoted from the CVE Program record.