Skip to content
vulnerability

CVE-2024-50302

5.5
Medium
KEV · Exploited in wildEPSS 0.81%Patch available

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.

exploited
Yes, in CISA KEV since 4 Mar 2025fix by 25 Mar 2025 (CISA deadline for US federal agencies)
fix
Fixed in < 3.12, >= 4.19.324 and <= 4.19.*, >= 5.4.286 and <= 5.4.* +6
likelihood
EPSS 0.81%
Published 19 Nov 2024Analysed here 2 Nov 2026CVSS scored by CISA

do firstUpgrade to a fixed release: < 3.12, >= 4.19.324 and <= 4.19.*, >= 5.4.286 and <= 5.4.*, >= 5.10.230 and <= 5.10.* (+5 more below).

triage
surface unknownruntimeWAF can block: noAV · localCWE-908· Common Weakness

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegritynoneavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
common questions

Is CVE-2024-50302 being exploited?

Yes. CVE-2024-50302 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-50302?

CVE-2024-50302 is rated Medium with a CVSS score of 5.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-50302?

Yes. A fix has been recorded for CVE-2024-50302. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-50302 affect?

CVE-2024-50302 affects google:android, debian:debian_linux, siemens:simatic_s7-1500_tm_mfp_firmware, siemens:sinec_os, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
google:androiddebian:debian_linuxsiemens:simatic_s7-1500_tm_mfp_firmwaresiemens:sinec_oslinux:linux_kernel
affected versions
Linux
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < e7ea60184e1e88a3c9e437b3265cbb6439aa7e26
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < 3f9e88f2672c4635960570ee9741778d4135ecf5
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < d7dc68d82ab3fcfc3f65322465da3d7031d4ab46
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < 05ade5d4337867929e7ef664e7ac8e0c734f1aaf
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < 1884ab3d22536a5c14b17c78c2ce76d1734e8b0b
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < 9d9f5c75c0c7f31766ec27d90f7a6ac673193191
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < 492015e6249fbcd42138b49de3c588d826dd9648
  • affected>= 27ce405039bfe6d3f4143415c638f56a3df77dca and < 177f25d1292c7e16e1199b39c85480f7f8815552
  • affectedb2b6cadad699d44a8a5b2a60f3d960e00d6fb3b7
  • affectedfe6c9b48ebc920ff21c10c50ab2729440c734254
  • affected>= 3.10.16 and < 3.11
  • affected>= 3.11.5 and < 3.12
  • affected3.12
vendor says fixed in< 3.12, >= 4.19.324 and <= 4.19.*, >= 5.4.286 and <= 5.4.*, >= 5.10.230 and <= 5.10.*, >= 5.15.172 and <= 5.15.*, >= 6.1.117 and <= 6.1.*, >= 6.6.61 and <= 6.6.*, >= 6.11.8 and <= 6.11.*, >= 6.12 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
active
automatable
no
technical impact
partial

Assessed by CISA 5 Mar 2025 (SSVC 2.0.3).

timeline

  1. 19 Nov 2024Published
  2. 4 Mar 2025Added to CISA KEV (exploited in the wild) · 105 days (about 4 months) later
  3. 5 Mar 2025CISA SSVC assessment: exploitation active · 1 day later
  4. 25 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
  5. 15 Oct 2026CVE record last updated · 569 days (about 2 years) later
  6. 2 Nov 2026Analysed by vulneraibility.com · 19 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
13 references in the CVE record: 13 links
Show 5 more

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved