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-49890capabilities: fix potential memleak on error path from vfs_getxattr_alloc()

Description

In the Linux kernel, the following vulnerability has been resolved: capabilities: fix potential memleak on error path from vfs_getxattr_alloc() In cap_inode_getsecurity(), we will use vfs_getxattr_alloc() to complete the memory allocation of tmpbuf, if we have completed the memory allocation of tmpbuf, but failed to call handler->get(...), there will be a memleak in below logic: |-- ret = (int)vfs_getxattr_alloc(mnt_userns, ...) | /* ^^^ alloc for tmpbuf */ |-- value = krealloc(*xattr_value, error + 1, flags) | /* ^^^ alloc memory */ |-- error = handler->get(handler, ...) | /* error! */ |-- *xattr_value = value | /* xattr_value is &tmpbuf (memory leak!) */ So we will try to free(tmpbuf) after vfs_getxattr_alloc() fails to fix it. [PM: subject line and backtrace tweaks]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 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

CVSS scores of CVE-2022-49890, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85
    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 90577bcc01c4188416a47269f8433f70502abe98
    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 0c3e6288da650d1ec911a259c77bc2d88e498603
    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < cdf01c807e974048c43c7fd3ca574f6086a57906
    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 2de8eec8afb75792440b8900a01d52b8f6742fd1
    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 7480aeff0093d8c54377553ec6b31110bea37b4d
    • affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 8cf0a1bc12870d148ae830a4ba88cfdf0e879cee
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 4.14.299 – ≤ 4.14.*
    • unaffected 4.19.265 – ≤ 4.19.*
    • unaffected 5.4.224 – ≤ 5.4.*
    • unaffected 5.10.154 – ≤ 5.10.*
    • unaffected 5.15.78 – ≤ 5.15.*
    • unaffected 6.0.8 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .