CVE-2024-35955: kprobes: Fix possible use-after-free issue on kprobe registration
Noroxi assessment
Priority: Monitor (action score 35/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: 1.1% (FIRST EPSS); higher than 67.6% of all records.
- Anyone who can reach it over the internet 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 2df2dd27066cdba8041e46a64362325626bdfb2e, 325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8, 36b57c7d2f8b7de224980f1a284432846ad71ca0; azl3 kernel 6.6.28.1-1 on Azure Linux 3.0 6.6.28.1-1; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.28.1-1.
Low priority for now. Upgrade to Linux Linux 2df2dd27066cdba8041e46a64362325626bdfb2e, 325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8, 36b57c7d2f8b7de224980f1a284432846ad71ca0; azl3 kernel 6.6.28.1-1 on Azure Linux 3.0 6.6.28.1-1; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.28.1-1 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: kprobes: Fix possible use-after-free issue on kprobe registration When unloading a module, its state is changing MODULE_STATE_LIVE -> MODULE_STATE_GOING -> MODULE_STATE_UNFORMED. Each change will take a time. `is_module_text_address()` and `__module_text_address()` works with MODULE_STATE_LIVE and MODULE_STATE_GOING. If we use `is_module_text_address()` and `__module_text_address()` separately, there is a chance that the first one is succeeded but the next one is failed because module->state becomes MODULE_STATE_UNFORMED between those operations. In `check_kprobe_address_safe()`, if the second `__module_text_address()` is failed, that is ignored because it expected a kernel_text address. But it may have failed simply because module->state has been changed to MODULE_STATE_UNFORMED. In this case, arm_kprobe() will try to modify non-exist module text address (use-after-free). To fix this problem, we should not use separated `is_module_text_address()` and `__module_text_address()`, but use only `__module_text_address()` once and do `try_module_get(module)` which is only available with MODULE_STATE_LIVE.
- Published
- May 20, 2024
- Updated
- Oct 15, 2026
- EPSS
- 1.1% · 67th percentile
- CWE
- CWE-416
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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.
Running WordPress? Scan your site free with WP Lens
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 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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel4.19.256 and later · before 4.19.313
- linux linux kernel5.4.211 and later · before 5.4.275
- linux linux kernel5.10.137 and later · before 5.10.216
- linux linux kernel5.15.61 and later · before 5.15.157
- linux linux kernel4.14.291 and later · before 4.15
- linux linux kernel5.19.2 and later · before 6.1.87
- linux linux kernel6.2 and later · before 6.6.28
- linux linux kernel6.7 and later · before 6.8.7
- linux linux kernel5.18.18 and later · before 5.19
- linux linux kernel6.9
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
- 4262b6eb057d86c7829168c541654fe0d48fdac8, 97e813e6a143edf4208e15c72199c495ed80cea5, 16a544f1e013ba0660612f3fe35393b143b19a84, 6.0affected
- 1c836bad43f3e2ff71cc397a6e6ccb4e7bd116f8 and later · before b5808d40093403334d939e2c3c417144d12a6f33affected · git
- 6a119c1a584aa7a2c6216458f1f272bf1bc93a93 and later · before 93eb31e7c3399e326259f2caa17be1e821f5a412affected · git
- 2a49b025c36ae749cee7ccc4b7e456e02539cdc3 and later · before 5062d1f4f07facbdade0f402d9a04a788f52e26daffected · git
- a1edb85e60fdab1e14db63ae8af8db3f0d798fb6 and later · before 2df2dd27066cdba8041e46a64362325626bdfb2eaffected · git
- 28f6c37a2910f565b4f5960df52b2eccae28c891 and later · before 62029bc9ff2c17a4e3a2478d83418ec575413808affected · git
- 28f6c37a2910f565b4f5960df52b2eccae28c891 and later · before d15023fb407337028a654237d8968fefdcf87c2faffected · git
- 28f6c37a2910f565b4f5960df52b2eccae28c891 and later · before 36b57c7d2f8b7de224980f1a284432846ad71ca0affected · git
- 28f6c37a2910f565b4f5960df52b2eccae28c891 and later · before 325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8affected · git
- 4.19.256 and later · before 4.19.313affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.90-1 | 6.1.90-1 |
| Debian:13 | linux | before 6.8.9-1 | 6.8.9-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-35950May 20, 2024 · drm/client: Fully protect modes[] with dev->mode_config.mutex22Monitor
- ← EarlierCVE-2024-35951May 20, 2024 · drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr()22Monitor
- Later →CVE-2024-35958May 20, 2024 · net: ena: Fix incorrect descriptor free behavior22Monitor
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 | 2df2dd27066cdba8041e46a64362325626bdfb2e | Vendor (CNA) |
| Linux Linux | 325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8 | Vendor (CNA) |
| Linux Linux | 36b57c7d2f8b7de224980f1a284432846ad71ca0 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.19.313 | Vendor (CNA) |
| Linux Linux | 5.10.216 | Vendor (CNA) |
| Linux Linux | 5.15.157 | Vendor (CNA) |
| Linux Linux | 5.19 | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 5.4.275 | Vendor (CNA) |
| Linux Linux | 5062d1f4f07facbdade0f402d9a04a788f52e26d | Vendor (CNA) |
| Linux Linux | 62029bc9ff2c17a4e3a2478d83418ec575413808 | Vendor (CNA) |
| Linux Linux | 93eb31e7c3399e326259f2caa17be1e821f5a412 | Vendor (CNA) |
| Linux Linux | b5808d40093403334d939e2c3c417144d12a6f33 | Vendor (CNA) |
| Linux Linux | d15023fb407337028a654237d8968fefdcf87c2f | Vendor (CNA) |
| azl3 kernel 6.6.28.1-1 on Azure Linux 3.0 | 6.6.28.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 | 6.6.28.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.157.1-1 on CBL Mariner 2.0 | 5.15.157.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.179.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL-Mariner 2.0 | 5.15.157.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.90-1 · Debian:12 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- git.kernel.org/stable/c/325f3fb551f8cd672dbbfc4cf58b14f9ee3fc9e8
- git.kernel.org/stable/c/36b57c7d2f8b7de224980f1a284432846ad71ca0
- git.kernel.org/stable/c/5062d1f4f07facbdade0f402d9a04a788f52e26d
- git.kernel.org/stable/c/62029bc9ff2c17a4e3a2478d83418ec575413808
- git.kernel.org/stable/c/93eb31e7c3399e326259f2caa17be1e821f5a412
- git.kernel.org/stable/c/b5808d40093403334d939e2c3c417144d12a6f33
- git.kernel.org/stable/c/d15023fb407337028a654237d8968fefdcf87c2f
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-613116.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.