CVE-2023-52510: ieee802154: ca8210: Fix a potential UAF in ca8210_probe

Published Mar 2, 2024
·
Updated

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

ieee802154: ca8210: Fix a potential UAF in ca8210probe

If ofclkaddprovider() fails in ca8210registerextclock(), it calls clkunregister() to release priv->clk and returns an error. However, the caller ca8210probe() then calls ca8210remove(), where priv->clk is freed again in ca8210unregisterextclock(). In this case, a use-after-free may happen in the second time we call clkunregister().

Fix this by removing the first clkunregister(). Also, priv->clk could be an error code on failure of clkregisterfixedrate(). Use ISERRORNULL to catch this case in ca8210unregisterextclock().

Affected Software

13 affected componentsFixes available
Linux Linux kernel>=4.12<4.14.328
Linux Linux kernel>=4.15<4.19.297
Linux Linux kernel>=4.20<5.4.259
Linux Linux kernel>=5.5<5.10.199
Linux Linux kernel>=5.11<5.15.136
Linux Linux kernel>=5.16<6.1.59
Linux Linux kernel>=6.2<6.5.8
Linux Linux kernel=6.6-rc1
Linux Linux kernel=6.6-rc2
Linux Linux kernel=6.6-rc3
Linux Linux kernel=6.6-rc4
Linux Linux kernel=6.6-rc5
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

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.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Compensating control

    In the Linux kernel ieee802154 ca8210 driver, remove the first clk_unregister() call in ca8210_register_ext_clock() and use IS_ERR_OR_NULL when checking priv->clk in ca8210_unregister_ext_clock() to prevent the second clk_unregister() from causing a use-after-free.

Event History

Mar 2, 2024
CVE Published
via MITRE·09:52 PM
Data Sourced
via MITRE·09:52 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2023-52510?

CVE-2023-52510 is categorized with medium severity due to the potential for a use-after-free condition.

2

How do I fix CVE-2023-52510?

To remediate CVE-2023-52510, ensure that your Linux Kernel version is updated to 5.10.223-1 or later.

3

Which Linux Kernel versions are affected by CVE-2023-52510?

CVE-2023-52510 impacts Linux Kernel versions from 4.12 up to 6.6-rc5.

4

What could happen if CVE-2023-52510 is exploited?

Exploitation of CVE-2023-52510 may lead to local privilege escalation or system instability.

5

Is there a patch available for CVE-2023-52510?

Yes, patches are available in the updates for various Linux Kernel versions, including 6.1.123-1 and 6.12.11-1.

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