Serialization hang via padata sequence-number misordering
Published Oct 21, 2024 · Updated Aug 5, 2026
Denial of service in Linux allows attackers to hang padata serialization after more than 2^32 object submissions to padata_do_serial. kernel/padata.c orders a wrapped seq_nr before older reorder-list entries, leaving padata_find_next unable to match the next sequence number with the processed counter. Triggering the deadlock requires over 4.29 billion serialized objects, and the resulting hang interrupts serialization without reported data disclosure or modification.
Summary
What happened
Denial of service in Linux allows attackers to hang padata serialization after more than 2^32 object submissions to padata_do_serial. kernel/padata.c orders a wrapped seq_nr before older reorder-list entries, leaving padata_find_next unable to match the next sequence number with the processed counter. Triggering the deadlock requires over 4.29 billion serialized objects, and the resulting hang interrupts serialization without reported data disclosure or modification.
The record
- CVE
- CVE-2024-47739
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <1b8cf11b3ca593a8802a51802cd0c28c38501428
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <1bd712de96ad7167fe0d608e706cd60587579f16
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <46c4079460f4dcaf445860679558eedef4e1bc91
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <72164d5b648951684b1a593996b37a6083c61d7d
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <9a22b2812393d93d84358a760c347c21939029a6
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <9e279e6c1f012b82628b89e1b9c65dbefa8ca25a
- Affected versionversion=bfde23ce200e6d33291d29b9b8b60cc2f30f0805 <ab205e1c3846326f162180e56825b4ba38ce9c30
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo