Answer in brief
CVE-2023-52509 records a High severity (CVSS 7.8) vulnerability in ravb: Fix use-after-free issue in ravb_tx_timeout_work(). 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c156633f1353264634135dea86ffcae74f2122fc <65d34cfd4e347054eb4193bc95d9da7eaa72dee5 || >=c156633f1353264634135dea86ffcae74f2122fc <db9aafa19547833240f58c2998aed7baf414dc82 || >=c156633f1353264634135dea86ffcae74f2122fc <616761cf9df9af838c0a1a1232a69322a9eb67e6 || >=c156633f1353264634135dea86ffcae74f2122fc <6f6fa8061f756aedb93af12a8a5d3cf659127965 || >=c156633f1353264634135dea86ffcae74f2122fc <105abd68ad8f781985113aee2e92e0702b133705 || >=c156633f1353264634135dea86ffcae74f2122fc <3971442870713de527684398416970cf025b4f89 | 65d34cfd4e347054eb4193bc95d9da7eaa72dee5, db9aafa19547833240f58c2998aed7baf414dc82, 616761cf9df9af838c0a1a1232a69322a9eb67e6, 6f6fa8061f756aedb93af12a8a5d3cf659127965, 105abd68ad8f781985113aee2e92e0702b133705, 3971442870713de527684398416970cf025b4f89 |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Mar 2, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ravb: Fix use-after-free issue in ravb_tx_timeout_work() The ravb_stop() should call cancel_work_sync(). Otherwise, ravb_tx_timeout_work() is possible to use the freed priv after ravb_remove() was called like below: CPU0 CPU1 ravb_tx_timeout() ravb_remove() unregister_netdev() free_netdev(ndev) // free priv ravb_tx_timeout_work() // use priv unregister_netdev() will call .ndo_stop() so that ravb_stop() is called. And, after phy_stop() is called, netif_carrier_off() is also called. So that .ndo_tx_timeout() will not be called after phy_stop().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-52509 records a High severity (CVSS 7.8) vulnerability in ravb: Fix use-after-free issue in ravb_tx_timeout_work(). 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c156633f1353264634135dea86ffcae74f2122fc <65d34cfd4e347054eb4193bc95d9da7eaa72dee5 || >=c156633f1353264634135dea86ffcae74f2122fc <db9aafa19547833240f58c2998aed7baf414dc82 || >=c156633f1353264634135dea86ffcae74f2122fc <616761cf9df9af838c0a1a1232a69322a9eb67e6 || >=c156633f1353264634135dea86ffcae74f2122fc <6f6fa8061f756aedb93af12a8a5d3cf659127965 || >=c156633f1353264634135dea86ffcae74f2122fc <105abd68ad8f781985113aee2e92e0702b133705 || >=c156633f1353264634135dea86ffcae74f2122fc <3971442870713de527684398416970cf025b4f89 | 65d34cfd4e347054eb4193bc95d9da7eaa72dee5, db9aafa19547833240f58c2998aed7baf414dc82, 616761cf9df9af838c0a1a1232a69322a9eb67e6, 6f6fa8061f756aedb93af12a8a5d3cf659127965, 105abd68ad8f781985113aee2e92e0702b133705, 3971442870713de527684398416970cf025b4f89 |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Mar 2, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ravb: Fix use-after-free issue in ravb_tx_timeout_work() The ravb_stop() should call cancel_work_sync(). Otherwise, ravb_tx_timeout_work() is possible to use the freed priv after ravb_remove() was called like below: CPU0 CPU1 ravb_tx_timeout() ravb_remove() unregister_netdev() free_netdev(ndev) // free priv ravb_tx_timeout_work() // use priv unregister_netdev() will call .ndo_stop() so that ravb_stop() is called. And, after phy_stop() is called, netif_carrier_off() is also called. So that .ndo_tx_timeout() will not be called after phy_stop().
Quoted source text, attributed separately from HOL analysis.