CVE-2024-44968: tick/broadcast: Move per CPU pointer access into the atomic section

Published Sep 4, 2024
·
Updated

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

tick/broadcast: Move per CPU pointer access into the atomic section

The recent fix for making the take over of the broadcast timer more reliable retrieves a per CPU pointer in preemptible context.

This went unnoticed as compilers hoist the access into the non-preemptible region where the pointer is actually used. But of course it's valid that the compiler keeps it at the place where the code puts it which rightfully triggers:

BUG: using smpprocessorid() in preemptible [00000000] code: caller is hotplugcpubroadcasttickpull+0x1c/0xc0

Move it to the actual usage site which is in a non-preemptible region.

Affected Software

8 affected componentsFixes available
Linux Linux kernel>=6.1.103<6.1.105
Linux Linux kernel>=6.6.44<6.6.46
Linux Linux kernel>=6.10.3<6.10.5
Linux Linux kernel=6.11-rc1
debian/linux<6.1.106-1
6.1.106-1
debian/linux<6.10.6-1
6.10.6-1
debian/linux<6.10.6-1
6.10.6-1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-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 6.1.106-1
  2. Upgrade

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

    Fixed in 6.10.6-1
  3. Upgrade

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

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
  4. Compensating control

    In tick/broadcast, move the per-CPU pointer access into the atomic, non-preemptible section where the pointer is actually used.

Event History

Sep 4, 2024
CVE Published
via MITRE·06:56 PM
Data Sourced
via MITRE·06:56 PM
Description
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·07:15 PM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-44968?

CVE-2024-44968 has a medium severity level due to its potential impact on system reliability.

2

How do I fix CVE-2024-44968?

To fix CVE-2024-44968, you should update the Linux kernel to a version that is not vulnerable, specifically above versions 6.1.105, 6.6.46, 6.10.5, or 6.11-rc1.

3

What systems are affected by CVE-2024-44968?

CVE-2024-44968 affects specific versions of the Linux kernel between 6.1.103 and 6.1.105, 6.6.44 and 6.6.46, 6.10.3 and 6.10.5, as well as version 6.11-rc1.

4

Is there a workaround for CVE-2024-44968?

No specific workaround is recommended for CVE-2024-44968; the best course of action is to apply the appropriate kernel update.

5

What type of vulnerability is CVE-2024-44968?

CVE-2024-44968 is a potential reliability issue within the Linux kernel related to the handling of per CPU pointers in preemptible contexts.

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