Answer in brief
CVE-2025-21915 records a Unknown severity vulnerability in cdx: Fix possible UAF error in driver_override_show(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2959ab247061e67485d83b6af8feb3761ec08cb9 <d7b339bbc887bcfc1a5b620bfc70c6fbb8f733bf || >=2959ab247061e67485d83b6af8feb3761ec08cb9 <8473135f89c0949436a22adb05b8cece2fb3da91 || >=2959ab247061e67485d83b6af8feb3761ec08cb9 <0439d541aa8d3444ad41c39e39eb71acb57acde3 || >=2959ab247061e67485d83b6af8feb3761ec08cb9 <91d44c1afc61a2fec37a9c7a3485368309391e0b | d7b339bbc887bcfc1a5b620bfc70c6fbb8f733bf, 8473135f89c0949436a22adb05b8cece2fb3da91, 0439d541aa8d3444ad41c39e39eb71acb57acde3, 91d44c1afc61a2fec37a9c7a3485368309391e0b |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Apr 1, 2025
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: cdx: Fix possible UAF error in driver_override_show() Fixed a possible UAF problem in driver_override_show() in drivers/cdx/cdx.c This function driver_override_show() is part of DEVICE_ATTR_RW, which includes both driver_override_show() and driver_override_store(). These functions can be executed concurrently in sysfs. The driver_override_store() function uses driver_set_override() to update the driver_override value, and driver_set_override() internally locks the device (device_lock(dev)). If driver_override_show() reads cdx_dev->driver_override without locking, it could potentially access a freed pointer if driver_override_store() frees the string concurrently. This could lead to printing a kernel address, which is a security risk since DEVICE_ATTR can be read by all users. Additionally, a similar pattern is used in drivers/amba/bus.c, as well as many other bus drivers, where device_lock() is taken in the show function, and it has been working without issues. This potential bug was detected by our experimental static analysis tool, which analyzes locking APIs and paired functions to identify data races and atomicity violations.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21915 records a Unknown severity vulnerability in cdx: Fix possible UAF error in driver_override_show(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2959ab247061e67485d83b6af8feb3761ec08cb9 <d7b339bbc887bcfc1a5b620bfc70c6fbb8f733bf || >=2959ab247061e67485d83b6af8feb3761ec08cb9 <8473135f89c0949436a22adb05b8cece2fb3da91 || >=2959ab247061e67485d83b6af8feb3761ec08cb9 <0439d541aa8d3444ad41c39e39eb71acb57acde3 || >=2959ab247061e67485d83b6af8feb3761ec08cb9 <91d44c1afc61a2fec37a9c7a3485368309391e0b | d7b339bbc887bcfc1a5b620bfc70c6fbb8f733bf, 8473135f89c0949436a22adb05b8cece2fb3da91, 0439d541aa8d3444ad41c39e39eb71acb57acde3, 91d44c1afc61a2fec37a9c7a3485368309391e0b |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Apr 1, 2025
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: cdx: Fix possible UAF error in driver_override_show() Fixed a possible UAF problem in driver_override_show() in drivers/cdx/cdx.c This function driver_override_show() is part of DEVICE_ATTR_RW, which includes both driver_override_show() and driver_override_store(). These functions can be executed concurrently in sysfs. The driver_override_store() function uses driver_set_override() to update the driver_override value, and driver_set_override() internally locks the device (device_lock(dev)). If driver_override_show() reads cdx_dev->driver_override without locking, it could potentially access a freed pointer if driver_override_store() frees the string concurrently. This could lead to printing a kernel address, which is a security risk since DEVICE_ATTR can be read by all users. Additionally, a similar pattern is used in drivers/amba/bus.c, as well as many other bus drivers, where device_lock() is taken in the show function, and it has been working without issues. This potential bug was detected by our experimental static analysis tool, which analyzes locking APIs and paired functions to identify data races and atomicity violations.
Quoted source text, attributed separately from HOL analysis.