CVE-2024-50012
cpufreq: Avoid a bad reference count on CPU node
Reported by linux · Published October 21, 2024
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Avoid a bad reference count on CPU node In the parse_perf_domain function, if the call to of_parse_phandle_with_args returns an error, then the reference to the CPU device node that was acquired at the start of the function would not be properly decremented. Address this by declaring the variable with the __free(device_node) cleanup attribute.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| bpftool | Amazon Linux | 6.1.119-129.201.amzn2023 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8486a32dd484a7d7ec25295c7439094608f54915, 8486a32dd484a7d7ec25295c7439094608f54915, 8486a32dd484a7d7ec25295c7439094608f54915 |
| Linux | Linux | 5.15, 0, 5.15.209 |
| amazon:2023 | bpftool | 0 |
| linux | linux_kernel | 5.15, 5.15, 5.15 |
| Linux | Linux | 5.15.209, 8486a32dd484a7d7ec25295c7439094608f54915, 8486a32dd484a7d7ec25295c7439094608f54915 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel-livepatch-6.1.119-129.201 | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | kernel | 0 |
Timeline
- Oct 21, 2024 CVE Published
- Oct 22, 2024 EPSS Score (30 in total, the first dated here)
- Oct 23, 2024 Coalition ESS Score (14 in total, the first dated here)
- Jan 2, 2026 Security Advisory (425 in total, the first dated here)
- Jan 2, 2026 CVE Updated
- Apr 29, 2026 Distribution Patch (358 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-50012
vulnetix vdb fixes CVE-2024-50012Or 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-50012/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart