CVE-2024-36481: tracing/probes: fix error check in parse_btf_field()
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.21% (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 4ed468edfeb54c7202e559eba74c25fac6a0dad0, ad4b202da2c498fefb69e5d87f67b946e7fe1e6a, e569eb34970281438e2b48a3ef11c87459fcfbcb; azl3 kernel 6.6.29.1-5 on Azure Linux 3.0 6.6.35.1-4; azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 6.6.35.1-4.
Low priority for now. Upgrade to Linux Linux 4ed468edfeb54c7202e559eba74c25fac6a0dad0, ad4b202da2c498fefb69e5d87f67b946e7fe1e6a, e569eb34970281438e2b48a3ef11c87459fcfbcb; azl3 kernel 6.6.29.1-5 on Azure Linux 3.0 6.6.35.1-4; azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 6.6.35.1-4 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: tracing/probes: fix error check in parse_btf_field() btf_find_struct_member() might return NULL or an error via the ERR_PTR() macro. However, its caller in parse_btf_field() only checks for the NULL condition. Fix this by using IS_ERR() and returning the error up the stack.
- Published
- Jun 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-754
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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
- 6.6affected
- c440adfbe30257dde905adc1fce51131145f7245 and later · before ad4b202da2c498fefb69e5d87f67b946e7fe1e6aaffected · git
- c440adfbe30257dde905adc1fce51131145f7245 and later · before 4ed468edfeb54c7202e559eba74c25fac6a0dad0affected · git
- c440adfbe30257dde905adc1fce51131145f7245 and later · before e569eb34970281438e2b48a3ef11c87459fcfbcbaffected · git
- before 6.6not affected · semver
- 6.6.33 and later · up to and including 6.6.*not affected · semver
- 6.9.4 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 6.6
- linux linux kernel6.6.1 and later · before 6.6.33
- linux linux kernel6.9 and later · before 6.9.4
- linux linux kernel6.10.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.9.7-1 | 6.9.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-34777Jun 21, 2024 · dma-mapping: benchmark: fix node id validation28Monitor
- ← EarlierCVE-2024-36477Jun 21, 2024 · tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer31Monitor
- Later →CVE-2024-39277Jun 21, 2024 · dma-mapping: benchmark: handle NUMA_NO_NODE correctly31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4ed468edfeb54c7202e559eba74c25fac6a0dad0 | Vendor (CNA) |
| Linux Linux | ad4b202da2c498fefb69e5d87f67b946e7fe1e6a | Vendor (CNA) |
| Linux Linux | e569eb34970281438e2b48a3ef11c87459fcfbcb | Vendor (CNA) |
| azl3 kernel 6.6.29.1-5 on Azure Linux 3.0 | 6.6.35.1-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 | 6.6.35.1-4 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.160.1-1 on CBL Mariner 2.0 | 5.15.160.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | 5.15.160.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.9.7-1 · Debian:13 | Package 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-2025-39682441 days aparttls: fix handling of zero-length records on the rx_listKEV70This week
- CVE-2024-4215939 days apartscsi: mpi3mr: Sanitise num_phys31Monitor
- CVE-2024-4216039 days apartf2fs: check validation of fault attrs in f2fs_build_fault_attr()31Monitor
- CVE-2024-4228457 days aparttipc: Return non-zero value from tipc_udp_addr2str() on error31Monitor
- CVE-2021-47014114 days apartnet/sched: act_ct: fix wild memory access when clearing fragments31Monitor
- CVE-2024-47727122 days apartx86/tdx: Fix "in-kernel MMIO" check31Monitor
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
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.