Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50749acct: fix potential integer overflow in encode_comp_t()

Description

In the Linux kernel, the following vulnerability has been resolved: acct: fix potential integer overflow in encode_comp_t() The integer overflow is descripted with following codes: > 317 static comp_t encode_comp_t(u64 value) > 318 { > 319 int exp, rnd; ...... > 341 exp <<= MANTSIZE; > 342 exp += value; > 343 return exp; > 344 } Currently comp_t is defined as type of '__u16', but the variable 'exp' is type of 'int', so overflow would happen when variable 'exp' in line 343 is greater than 65535.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e93f995a591c352d35d89c518c54f790e1537754
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < cf60bbca1b83a7e0927e36dbf178328982927886
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1750a0983c455a9b3badd848471fc8d58cb61f67
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a815a3e019456c94b03bd183e7ac22fd29e9e6fd
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6edd0cdee5780fd5f43356b72b29a2a6d48ef6da
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ebe16676e1dcaa4556ec4d36ca40c82e99e88cfa
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2224897d8187dc22a83e05d9361efcccf67bcf12
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0aac6e60c464a5f942f995428e67f8ae1c422250
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c5f31c655bcc01b6da53b836ac951c1556245305
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50749 badge
[![CVE-2022-50749](https://cveledger.app/badge/CVE-2022-50749.svg)](https://cveledger.app/cve/CVE-2022-50749)

Record last updated .