Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-38613: m68k: Fix spinlock race in kernel thread creation

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 0d9ae1253535f6e85a016e09c25ecbe6f7f59ef0, 2a8d1d95302c7d52c6ac8fa5cb4a6948ae0d3a14, 4eeffecc8e3cce25bb559502c2fd94a948bcde82.

Low priority for now. Upgrade to Linux Linux 0d9ae1253535f6e85a016e09c25ecbe6f7f59ef0, 2a8d1d95302c7d52c6ac8fa5cb4a6948ae0d3a14, 4eeffecc8e3cce25bb559502c2fd94a948bcde82 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: m68k: Fix spinlock race in kernel thread creation Context switching does take care to retain the correct lock owner across the switch from 'prev' to 'next' tasks. This does rely on interrupts remaining disabled for the entire duration of the switch. This condition is guaranteed for normal process creation and context switching between already running processes, because both 'prev' and 'next' already have interrupts disabled in their saved copies of the status register. The situation is different for newly created kernel threads. The status register is set to PS_S in copy_thread(), which does leave the IPL at 0. Upon restoring the 'next' thread's status register in switch_to() aka resume(), interrupts then become enabled prematurely. resume() then returns via ret_from_kernel_thread() and schedule_tail() where run queue lock is released (see finish_task_switch() and finish_lock_switch()). A timer interrupt calling scheduler_tick() before the lock is released in finish_task_switch() will find the lock already taken, with the current task as lock owner. This causes a spinlock recursion warning as reported by Guenter Roeck. As far as I can ascertain, this race has been opened in commit 533e6903bea0 ("m68k: split ret_from_fork(), simplify kernel_thread()") but I haven't done a detailed study of kernel history so it may well predate that commit. Interrupts cannot be disabled in the saved status register copy for kernel threads (init will complain about interrupts disabled when finally starting user space). Disable interrupts temporarily when switching the tasks' register sets in resume(). Note that a simple oriw 0x700,%sr after restoring sr is not enough here - this leaves enough of a race for the 'spinlock recursion' warning to still be observed. Tested on ARAnyM and qemu (Quadra 800 emulation).

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Jun 19, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-38613

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.7 and later · before 4.19.316
  • linux linux kernel4.20 and later · before 5.4.278
  • linux linux kernel5.5 and later · before 5.10.219
  • linux linux kernel5.11 and later · before 5.15.161
  • linux linux kernel5.16 and later · before 6.1.93
  • linux linux kernel6.2 and later · before 6.6.33
  • linux linux kernel6.7 and later · before 6.8.12
  • linux linux kernel6.9 and later · before 6.9.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.7affected
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before 2a8d1d95302c7d52c6ac8fa5cb4a6948ae0d3a14affected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before 5213cc01d0464c011fdc09f318705603ed3a746baffected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before 4eeffecc8e3cce25bb559502c2fd94a948bcde82affected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before 77b2b67a0f8bce260c53907e5749d61466d90c87affected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before 0d9ae1253535f6e85a016e09c25ecbe6f7f59ef0affected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before f3baf0f4f92af32943ebf27b960e0552c6c082fdaffected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before f1d4274a84c069be0f6098ab10c3443fc1f7134caffected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before 95f00caf767b5968c2c51083957b38be4748a78aaffected · git
    • 533e6903bea0440816a0f517b0845ccea4cc7917 and later · before da89ce46f02470ef08f0f580755d14d547da59edaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.8.12-16.8.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-38610Jun 19, 2024 · drivers/virt/acrn: fix PFNMAP PTE checks in acrn_vm_ram_map()
    31Monitor
  • ← EarlierCVE-2024-38611Jun 19, 2024 · media: i2c: et8ek8: Don't strip remove function when driver is builtin
    22Monitor
  • Later →CVE-2024-38614Jun 19, 2024 · openrisc: traps: Don't send signals to kernel mode threads
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0d9ae1253535f6e85a016e09c25ecbe6f7f59ef0Vendor (CNA)
Linux Linux2a8d1d95302c7d52c6ac8fa5cb4a6948ae0d3a14Vendor (CNA)
Linux Linux4eeffecc8e3cce25bb559502c2fd94a948bcde82Vendor (CNA)
Linux Linux5213cc01d0464c011fdc09f318705603ed3a746bVendor (CNA)
Linux Linux77b2b67a0f8bce260c53907e5749d61466d90c87Vendor (CNA)
Linux Linux95f00caf767b5968c2c51083957b38be4748a78aVendor (CNA)
Linux Linuxda89ce46f02470ef08f0f580755d14d547da59edVendor (CNA)
Linux Linuxf1d4274a84c069be0f6098ab10c3443fc1f7134cVendor (CNA)
Linux Linuxf3baf0f4f92af32943ebf27b960e0552c6c082fdVendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records