Review reviewHigh

CVE-2023-52509

Linux Linux, linux kernel

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 calle...

CVSS
7.8
EPSS
0.24%
15.4% percentile
CISA KEV
Not listed
Published
2024.03.03
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.24%
Technical severityCVSS 7.8

Vulnerability overview

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 calle...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= c156633f1353264634135dea86ffcae74f2122fc < 65d34cfd4e347054eb4193bc95d9da7eaa72dee5, >= c156633f1353264634135dea86ffcae74f2122fc < db9aafa19547833240f58c2998aed7baf414dc82, >= c156633f1353264634135dea86ffcae74f2122fc < 616761cf9df9af838c0a1a1232a69322a9eb67e6, >= c156633f1353264634135dea86ffcae74f2122fc < 6f6fa8061f756aedb93af12a8a5d3cf659127965, >= c156633f1353264634135dea86ffcae74f2122fc < 105abd68ad8f781985113aee2e92e0702b133705, >= c156633f1353264634135dea86ffcae74f2122fc < 3971442870713de527684398416970cf025b4f89, >= 4.2, >= 4.2 < 5.4.259, >= 5.5 < 5.10.199, >= 5.11 < 5.15.136, >= 5.16 < 6.1.59, >= 6.2 < 6.5.8, 6.6
Fixed versions
5.4.259, 5.10.199, 5.15.136, 6.1.59, 6.5.8

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
CVE-2023-52509 — Linux Linux, linux kernel | SECUFOCUS NOW