LiveActive security incident?Get immediate response
CVE Record

CVE-2024-47739: padata: use integer wrap around to prevent deadlock on seq_nr overflow

In the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata->seq_nr and pd->processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel sequencing flaw can deadlock parallel-data serialization after more than 2^32 objects are submitted. Affected systems may lose availability because processing stops, but the supplied sources show no confidentiality or integrity impact. Reaching the failure depends on sustained use of the kernel's padata subsystem.

Executive priority

Treat as a high-priority availability issue for exposed, high-throughput Linux workloads. Accelerate kernel updates where padata use is confirmed or uncertain; otherwise handle through the normal risk-based kernel patch cycle. No evidence supplied supports emergency incident response for active exploitation.

Technical view

The padata reorder logic mishandles a 32-bit seq_nr wraparound. An overflowed object can sort before outstanding objects, leaving padata_find_next unable to reconcile the next sequence number with the processed counter and deadlocking serialization. The kernel fix applies unsigned wraparound-aware ordering.

Likely exposure

Exposure requires an affected Linux kernel and a workload exercising padata_do_serial enough to exceed 2^32 submissions. Long-lived, high-throughput systems using padata are the clearest concern. The supplied affected-version data is ambiguous, so distribution-specific package status should determine exposure.

Exploitation context

The CVSS 3.1 score is 7.5 for network-reachable availability impact, but practical reachability depends on software paths that drive padata. The record is not in KEV, and the supplied sources do not establish active exploitation or a public exploit.

Researcher notes

The trigger is sequence exhaustion after more than 2^32 padata objects, not merely malformed input. Assess reachable kernel consumers, throughput, uptime, and counter lifecycle. The flattened affected-version list does not provide reliable range semantics; validate fixes through distribution advisories or commit inclusion rather than interpreting it as exact boundaries.

Mitigation direction

  • Apply a vendor-supported kernel update containing the referenced padata fix.
  • Check Linux distribution advisories for the corrected package version.
  • Follow vendor restart or reboot guidance after installing the kernel update.
  • Prioritize long-lived, high-throughput systems known to exercise padata.

Validation and detection

  • Inventory running kernel versions, not only installed kernel packages.
  • Compare each distribution package against its vendor advisory and fixed build.
  • Confirm the referenced fix is present when maintaining a custom kernel.
  • After updating, verify systems booted into the intended corrected kernel.
  • Monitor affected workloads for serialization stalls or unexplained availability loss.
Prepared
Confidence
medium
Sources
7

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-47739 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
2ADP providers
10Source 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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbfde23ce200e6d33291d29b9b8b60cc2f30f0805, bfde23ce200e6d33291d29b9b8b60cc2f30f0805, bfde23ce200e6d33291d29b9b8b60cc2f30f0805, bfde23ce200e6d33291d29b9b8b60cc2f30f0805, bfde23ce200e6d33291d29b9b8b60cc2f30f0805, bfde23ce200e6d33291d29b9b8b60cc2f30f0805, bfde23ce200e6d33291d29b9b8b60cc2f30f0805unaffected
LinuxLinux5.4, 0, 5.10.227, 5.15.168, 6.1.113, 6.6.54, 6.10.13, 6.11.2, 6.12affected
Weakness

CWE details

No CWE listed

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