Answer in brief
CVE-2024-39495 records a Unknown severity vulnerability in greybus: Fix use-after-free bug in gb_interface_release due to race condition.. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-39495 records a Unknown severity vulnerability in greybus: Fix use-after-free bug in gb_interface_release due to race condition.. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <74cd0a421896b2e07eafe7da4275302bfecef201 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <fb071f5c75d4b1c177824de74ee75f9dd34123b9 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <9a733d69a4a59c2d08620e6589d823c24be773dc || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <0b8fba38bdfb848fac52e71270b2aa3538c996ea || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <03ea2b129344152157418929f06726989efc0445 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ce | 74cd0a421896b2e07eafe7da4275302bfecef201, 2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83, fb071f5c75d4b1c177824de74ee75f9dd34123b9, 9a733d69a4a59c2d08620e6589d823c24be773dc, 0b8fba38bdfb848fac52e71270b2aa3538c996ea, 03ea2b129344152157418929f06726989efc0445, 5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ce |
| Linux/Linuxgeneric | 4.9 | Not reported |
| linux/linux_kernelgeneric | >=0 <74cd0a421896 || >=1da177e4c3f4 <2b6bb0b4abfd || >=1da177e4c3f4 <fb071f5c75d4 || >=1da177e4c3f4 <9a733d69a4a5 || >=1da177e4c3f4 <0b8fba38bdfb || >=1da177e4c3f4 <03ea2b129344 || >=1da177e4c3f4 <5c9c5d7f26ac | 74cd0a421896, 2b6bb0b4abfd, fb071f5c75d4, 9a733d69a4a5, 0b8fba38bdfb, 03ea2b129344, 5c9c5d7f26ac |
Published upstream
Jul 12, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <74cd0a421896b2e07eafe7da4275302bfecef201 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <fb071f5c75d4b1c177824de74ee75f9dd34123b9 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <9a733d69a4a59c2d08620e6589d823c24be773dc || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <0b8fba38bdfb848fac52e71270b2aa3538c996ea || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <03ea2b129344152157418929f06726989efc0445 || >=55742d2a071a569bf20f90d37b1b5b8a25a3f882 <5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ce | 74cd0a421896b2e07eafe7da4275302bfecef201, 2b6bb0b4abfd79b8698ee161bb73c0936a2aaf83, fb071f5c75d4b1c177824de74ee75f9dd34123b9, 9a733d69a4a59c2d08620e6589d823c24be773dc, 0b8fba38bdfb848fac52e71270b2aa3538c996ea, 03ea2b129344152157418929f06726989efc0445, 5c9c5d7f26acc2c669c1dcf57d1bb43ee99220ce |
| Linux/Linuxgeneric | 4.9 | Not reported |
| linux/linux_kernelgeneric | >=0 <74cd0a421896 || >=1da177e4c3f4 <2b6bb0b4abfd || >=1da177e4c3f4 <fb071f5c75d4 || >=1da177e4c3f4 <9a733d69a4a5 || >=1da177e4c3f4 <0b8fba38bdfb || >=1da177e4c3f4 <03ea2b129344 || >=1da177e4c3f4 <5c9c5d7f26ac | 74cd0a421896, 2b6bb0b4abfd, fb071f5c75d4, 9a733d69a4a5, 0b8fba38bdfb, 03ea2b129344, 5c9c5d7f26ac |
Published upstream
Jul 12, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.