LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42249: spi: don't unoptimize message in spi_async()

In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message() in spi_async() is wrong because the message is likely to be in the queue and not transferred yet. This can corrupt the message while it is being used by the controller driver. spi_maybe_unoptimize_message() is already called in the correct place in spi_finalize_current_message() to balance the call to spi_maybe_optimize_message() in spi_async().

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel SPI flaw can corrupt an asynchronous message while a hardware controller is still using it. A local, low-privileged attacker may be able to compromise confidentiality, integrity, and availability. Systems using affected kernels and SPI hardware deserve prompt review, especially appliances and embedded devices.

Executive priority

Treat as a high-priority maintenance issue for exposed embedded and hardware-control systems, but not as an internet-wide emergency. Inventory immediately and schedule vendor-supported kernel updates promptly. Escalate priority where untrusted local users or workloads can access SPI-related functionality.

Technical view

spi_async() incorrectly called spi_maybe_unoptimize_message() after queuing a message but potentially before its transfer completed. That premature change could corrupt controller-visible message state. The fix leaves unoptimization to spi_finalize_current_message(), where it correctly balances the earlier optimization call.

Likely exposure

The supplied record identifies Linux 6.9-related versions, including 6.9.10 and 6.10 metadata, as affected. Its version encoding is not sufficiently clear to define every vulnerable release. Practical exposure requires an affected kernel, relevant SPI functionality, and local low-privileged access.

Exploitation context

CVSS 3.1 is 7.8 with local access, low complexity, low privileges, and no user interaction. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Remote network-only exposure is not supported by these sources.

Researcher notes

The core defect is incorrect message lifecycle handling during asynchronous SPI processing. The sources establish possible message corruption but do not document a demonstrated exploitation primitive, affected controller drivers, or observed attacks. Distribution backports may make upstream version-only checks unreliable; validate by vendor advisory or commit inclusion.

Mitigation direction

  • Identify systems running Linux 6.9-series or 6.10 kernels with SPI functionality.
  • Apply a vendor-supported kernel containing the referenced upstream stable fix.
  • Prioritize embedded, appliance, and hardware-control systems where SPI is actively used.
  • If updates are unavailable, obtain product-specific mitigation guidance from the Linux distributor or device vendor.

Validation and detection

  • Record each system's kernel version, distribution build, architecture, and enabled SPI drivers.
  • Compare vendor changelogs against CVE-2024-42249 and the referenced stable commits.
  • Confirm the installed kernel package includes the fix, rather than relying only on upstream version numbers.
  • After updating, reboot into the corrected kernel and verify the running version.
  • Review kernel logs for SPI controller errors or unexplained instability; absence does not prove safety.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42249 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-42249Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02, 7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02unaffected
LinuxLinux6.9, 0, 6.9.10, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.