CVE-2022-49890capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
- 5.5MediumCVSS base score
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
ID reserved
By Linux
Published
- 13 months later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS: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
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 90577bcc01c4188416a47269f8433f70502abe98
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 0c3e6288da650d1ec911a259c77bc2d88e498603
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < cdf01c807e974048c43c7fd3ca574f6086a57906
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 2de8eec8afb75792440b8900a01d52b8f6742fd1
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 7480aeff0093d8c54377553ec6b31110bea37b4d
- affected 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 – < 8cf0a1bc12870d148ae830a4ba88cfdf0e879cee
- 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
- https://git.kernel.org/stable/c/6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85 (opens in a new tab)
- https://git.kernel.org/stable/c/90577bcc01c4188416a47269f8433f70502abe98 (opens in a new tab)
- https://git.kernel.org/stable/c/0c3e6288da650d1ec911a259c77bc2d88e498603 (opens in a new tab)
- https://git.kernel.org/stable/c/cdf01c807e974048c43c7fd3ca574f6086a57906 (opens in a new tab)
- https://git.kernel.org/stable/c/2de8eec8afb75792440b8900a01d52b8f6742fd1 (opens in a new tab)
- https://git.kernel.org/stable/c/7480aeff0093d8c54377553ec6b31110bea37b4d (opens in a new tab)
- https://git.kernel.org/stable/c/8cf0a1bc12870d148ae830a4ba88cfdf0e879cee (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-12880 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49890)Record last updated .