VDB

CVE-2024-50002

CVE-2024-50002 PUBLISHED

static_call: Handle module init failure correctly in static_call_del_module()

Reported by linux · Published October 21, 2024

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.

Affected products

VendorProductVersions
LinuxLinux9183c3f9ed710a8edf1a61e8a96d497258d26e08, 9183c3f9ed710a8edf1a61e8a96d497258d26e08, 9183c3f9ed710a8edf1a61e8a96d497258d26e08
LinuxLinux5.10, 0, 5.15.168
linuxlinux_kernel5.10, 5.10, 5.10
amazon:2023perf0
amazon:2023kernel-tools0
LinuxLinux0, 9183c3f9ed710a8edf1a61e8a96d497258d26e08, 9183c3f9ed710a8edf1a61e8a96d497258d26e08
amazon:2023kernel-libbpf0
amazon:2023kernel-tools-devel0
amazon:2023python3-perf0
amazon:2023kernel-livepatch-6.1.115-126.1970
amazon:2023kernel-modules-extra0
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-headers0
amazon:2023kernel-libbpf-static0
amazon:2023kernel-devel0
amazon:2023kernel-modules-extra-common0
amazon:2023kernel0
amazon:2023bpftool0

Timeline

  • Oct 21, 2024 CVE Published
  • Oct 22, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 22, 2024 Coalition ESS Score (11 in total, the first dated here)
  • Dec 16, 2025 PoC Published
  • Jan 2, 2026 Security Advisory (449 in total, the first dated here)
  • Mar 30, 2026 Distribution Patch (381 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-50002
vulnetix vdb fixes CVE-2024-50002

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-50002/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›