Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50002: static_call: Handle module init failure correctly in static_call_del_module()

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2b494471797bff3d257e99dc0a7abb0c5ff3b4cd, 4b30051c4864234ec57290c3d142db7c88f10d8a, 9c48c2b53191bf991361998f5bb97b8f2fc5a89c; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2.

Low priority for now. Upgrade to Linux Linux 2b494471797bff3d257e99dc0a7abb0c5ff3b4cd, 4b30051c4864234ec57290c3d142db7c88f10d8a, 9c48c2b53191bf991361998f5bb97b8f2fc5a89c; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it's part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod *mods; struct static_call_site *sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it's a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can't match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.

Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-50002

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.10affected
    • 9183c3f9ed710a8edf1a61e8a96d497258d26e08 and later · before ed4c8ce0f307f2ab8778aeb40a8866d171e8f128affected · git
    • 9183c3f9ed710a8edf1a61e8a96d497258d26e08 and later · before b566c7d8a2de403ccc9d8a06195e19bbb386d0e4affected · git
    • 9183c3f9ed710a8edf1a61e8a96d497258d26e08 and later · before c0abbbe8c98c077292221ec7e2baa667c9f0974caffected · git
    • 9183c3f9ed710a8edf1a61e8a96d497258d26e08 and later · before 2b494471797bff3d257e99dc0a7abb0c5ff3b4cdaffected · git
    • 9183c3f9ed710a8edf1a61e8a96d497258d26e08 and later · before 9c48c2b53191bf991361998f5bb97b8f2fc5a89caffected · git
    • 9183c3f9ed710a8edf1a61e8a96d497258d26e08 and later · before 4b30051c4864234ec57290c3d142db7c88f10d8aaffected · git
    • before 5.10not affected · semver
    • 5.15.168 and later · up to and including 5.15.*not affected · semver
    • 6.1.113 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-49999Oct 21, 2024 · afs: Fix the setting of the server responding flag
    22Monitor
  • ← EarlierCVE-2024-50000Oct 21, 2024 · net/mlx5e: Fix NULL deref in mlx5e_tir_builder_alloc()
    22Monitor
  • Later →CVE-2024-50003Oct 21, 2024 · drm/amd/display: Fix system hang while resume with TBT monitor
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2b494471797bff3d257e99dc0a7abb0c5ff3b4cdVendor (CNA)
Linux Linux4b30051c4864234ec57290c3d142db7c88f10d8aVendor (CNA)
Linux Linux9c48c2b53191bf991361998f5bb97b8f2fc5a89cVendor (CNA)
Linux Linuxb566c7d8a2de403ccc9d8a06195e19bbb386d0e4Vendor (CNA)
Linux Linuxc0abbbe8c98c077292221ec7e2baa667c9f0974cVendor (CNA)
Linux Linuxed4c8ce0f307f2ab8778aeb40a8866d171e8f128Vendor (CNA)
azl3 kernel 6.6.51.1-5 on Azure Linux 3.06.6.57.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.57.1-2 on Azure Linux 3.06.6.57.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-500010 days apartnet/mlx5: Fix error path in multi-packet WQE transmit
    22Monitor
  • CVE-2024-5017618 days apartremoteproc: k3-r5: Fix error handling when power-up failed
    22Monitor
  • CVE-2024-5020218 days apartnilfs2: propagate directory read errors from nilfs_find_entry()
    22Monitor
  • CVE-2024-5306329 days apartmedia: dvbdev: prevent the risk of out of memory access
    22Monitor
  • CVE-2022-48673171 days apartnet/smc: Fix possible access to freed memory in link clear
    22Monitor
  • CVE-2021-46928237 days apartparisc: Clear stale IIR value on instruction access rights trap
    22Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records