CVE-2024-39495: greybus: Fix use-after-free bug in gb_interface_release due to race condition.
Noroxi assessment
Priority: Monitor (action score 31/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.32% (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 03ea2b129344152157418929f06726989efc0445, 0b8fba38bdfb848fac52e71270b2aa3538c996ea, 2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 kernel 6.6.35.1-1 on Azure Linux 3.0 6.6.35.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 03ea2b129344152157418929f06726989efc0445, 0b8fba38bdfb848fac52e71270b2aa3538c996ea, 2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-1; azl3 kernel 6.6.35.1-1 on Azure Linux 3.0 6.6.35.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: greybus: Fix use-after-free bug in gb_interface_release due to race condition. In gb_interface_create, &intf->mode_switch_completion is bound with gb_interface_mode_switch_work. Then it will be started by gb_interface_request_mode_switch. Here is the relevant code. if (!queue_work(system_long_wq, &intf->mode_switch_work)) { ... } If we call gb_interface_release to make cleanup, there may be an unfinished work. This function will call kfree to free the object "intf". However, if gb_interface_mode_switch_work is scheduled to run after kfree, it may cause use-after-free error as gb_interface_mode_switch_work will use the object "intf". The possible execution flow that may lead to the issue is as follows: CPU0 CPU1 | gb_interface_create | gb_interface_request_mode_switch gb_interface_release | kfree(intf) (free) | | gb_interface_mode_switch_work | mutex_lock(&intf->mutex) (use) Fix it by canceling the work before kfree.
- Published
- Jul 12, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.4.279
- linux linux kernel5.5 and later · before 5.10.221
- linux linux kernel5.11 and later · before 5.15.162
- linux linux kernel5.16 and later · before 6.1.95
- linux linux kernel6.2 and later · before 6.6.35
- linux linux kernel6.7 and later · before 6.9.6
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
- 4.9affected
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before 74cd0a421896b2e07eafe7da4275302bfecef201affected · git
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before 2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83affected · git
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before fb071f5c75d4b1c177824de74ee75f9dd34123b9affected · git
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before 9a733d69a4a59c2d08620e6589d823c24be773dcaffected · git
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before 0b8fba38bdfb848fac52e71270b2aa3538c996eaaffected · git
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before 03ea2b129344152157418929f06726989efc0445affected · git
- 55742d2a071a569bf20f90d37b1b5b8a25a3f882 and later · before 5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ceaffected · git
- before 4.9not affected · semver
- 5.4.279 and later · up to and including 5.4.*not affected · 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.99-1 | 6.1.99-1 |
| 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-39493Jul 10, 2024 · crypto: qat - Fix ADF_DEV_RESET_SYNC memory leak22Monitor
- ← EarlierCVE-2024-39494Jul 12, 2024 · ima: Fix use-after-free on a dentry's dname.name31Monitor
- Later →CVE-2024-39496Jul 12, 2024 · btrfs: zoned: fix use-after-free due to race with dev replace31Monitor
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 | 03ea2b129344152157418929f06726989efc0445 | Vendor (CNA) |
| Linux Linux | 0b8fba38bdfb848fac52e71270b2aa3538c996ea | Vendor (CNA) |
| Linux Linux | 2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83 | Vendor (CNA) |
| Linux Linux | 5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ce | Vendor (CNA) |
| Linux Linux | 74cd0a421896b2e07eafe7da4275302bfecef201 | Vendor (CNA) |
| Linux Linux | 9a733d69a4a59c2d08620e6589d823c24be773dc | Vendor (CNA) |
| Linux Linux | fb071f5c75d4b1c177824de74ee75f9dd34123b9 | Vendor (CNA) |
| azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 | 6.6.35.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.35.1-1 on Azure Linux 3.0 | 6.6.35.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.160.1-1 on CBL Mariner 2.0 | 5.15.162.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.160.1-1 on CBL-Mariner 2.0 | 5.15.162.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.162.2-1 on CBL Mariner 2.0 | 5.15.162.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.99-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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0942 · Jul 16, 2024(Linux Kernel Güncellemesi)
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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 (7 more)Show less
- git.kernel.org/stable/c/0b8fba38bdfb848fac52e71270b2aa3538c996ea
- git.kernel.org/stable/c/2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83
- git.kernel.org/stable/c/5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ce
- git.kernel.org/stable/c/74cd0a421896b2e07eafe7da4275302bfecef201
- git.kernel.org/stable/c/9a733d69a4a59c2d08620e6589d823c24be773dc
- git.kernel.org/stable/c/fb071f5c75d4b1c177824de74ee75f9dd34123b9
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.