Incorrect process accounting via exponent overflow
Published Dec 24, 2025 · Updated Dec 24, 2025
Integer overflow in Linux kernel process accounting allows local users to produce incorrect records through oversized metric values. The encode_comp_t() path packs an exponent and mantissa into 16-bit comp_t but fails to saturate when the exponent exceeds its representable range. The flaw is reached only when process accounting is enabled and a recorded process metric grows large enough to cross that limit.
Summary
What happened
Integer overflow in Linux kernel process accounting allows local users to produce incorrect records through oversized metric values. The encode_comp_t() path packs an exponent and mantissa into 16-bit comp_t but fails to saturate when the exponent exceeds its representable range. The flaw is reached only when process accounting is enabled and a recorded process metric grows large enough to cross that limit.
The record
- CVE
- CVE-2022-50749
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0aac6e60c464a5f942f995428e67f8ae1c422250
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1750a0983c455a9b3badd848471fc8d58cb61f67
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2224897d8187dc22a83e05d9361efcccf67bcf12
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6edd0cdee5780fd5f43356b72b29a2a6d48ef6da
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a815a3e019456c94b03bd183e7ac22fd29e9e6fd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c5f31c655bcc01b6da53b836ac951c1556245305
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cf60bbca1b83a7e0927e36dbf178328982927886
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e93f995a591c352d35d89c518c54f790e1537754
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ebe16676e1dcaa4556ec4d36ca40c82e99e88cfa
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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