CVE-2024-49982: aoe: fix the potential use-after-free problem in more places

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

aoe: fix the potential use-after-free problem in more places

For fixing CVE-2023-6270, f98364e92662 ("aoe: fix the potential use-after-free problem in aoecmdcfgpkts") makes tx() calling devput() instead of doing in aoecmdcfgpkts(). It avoids that the tx() runs into use-after-free.

Then Nicolai Stange found more places in aoe have potential use-after-free problem with tx(). e.g. revalidate(), aoecmdatarw(), resend(), probe() and aoecmdcfgrsp(). Those functions also use aoenetxmit() to push packet to tx queue. So they should also use devhold() to increase the refcnt of skb->dev.

On the other hand, moving devput() to tx() causes that the refcnt of skb->dev be reduced to a negative value, because corresponding devhold() are not called in revalidate(), aoecmdatarw(), resend(), probe(), and aoecmdcfgrsp(). This patch fixed this issue.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

12 affected componentsFixes available
Linux Linux kernel>=5.10.214<5.10.227
Linux Linux kernel>=5.15.153<5.15.168
Linux Linux kernel>=6.1.83<6.1.113
Linux Linux kernel>=6.6.23<6.6.55
Linux Linux kernel>=6.7.11<6.8.2
Linux Linux kernel>=6.9<6.10.14
Linux Linux kernel>=6.11<6.11.3
Linux Linux kernel=4.19.311
Linux Linux kernel=5.4.273
Linux Linux kernel=6.12-rc1
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch f98364e92662
  4. Configuration

    In the AOE driver, after changing tx() to call dev_put() (per patch f98364e92662), also add/ensure matching dev_hold() calls so the refcnt of skb->dev is increased in revalidate(), aoecmd_ata_rw(), resend(), probe(), and aoecmd_cfg_rsp(), avoiding refcnt going negative and preventing use-after-free.

    Linux kernel (aoe driver) dev_put() / dev_hold() refcount handling = Use dev_hold() in revalidate(), aoecmd_ata_rw(), resend(), probe(), and aoecmd_cfg_rsp() in addition to ensuring dev_put() is called in tx()

Event History

Oct 21, 2024
CVE Published
via MITRE·06:02 PM
Data Sourced
via MITRE·06:02 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 16, 2025
Data Sourced
via Launchpad·06:12 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·06:30 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-49982?

The severity of CVE-2024-49982 is classified as high due to the potential for use-after-free vulnerabilities in the Linux kernel.

2

How do I fix CVE-2024-49982?

To fix CVE-2024-49982, upgrade to the latest patched versions of the Linux kernel provided by your distribution.

3

Which versions of the Linux kernel are affected by CVE-2024-49982?

CVE-2024-49982 affects Linux kernel versions between 4.19.311 and 6.12-rc1, along with specific versions in between.

4

What types of systems are impacted by CVE-2024-49982?

CVE-2024-49982 primarily impacts systems running specific versions of the Linux kernel across various Linux distributions.

5

Are there any workarounds for CVE-2024-49982?

There are no recommended workarounds for CVE-2024-49982, so applying the security patch is essential.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203