CVE-2022-49890: capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
First published: Thu May 01 2025(Updated: )
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]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Linux Kernel | >=4.14<4.14.299 | |
| Linux Kernel | >=4.15<4.19.265 | |
| Linux Kernel | >=4.20<5.4.224 | |
| Linux Kernel | >=5.5<5.10.154 | |
| Linux Kernel | >=5.11<5.15.78 | |
| Linux Kernel | >=5.16<6.0.8 | |
| Linux Kernel | =6.1-rc1 | |
| Linux Kernel | =6.1-rc2 | |
| Linux Kernel | =6.1-rc3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85
- https://git.kernel.org/stable/c/90577bcc01c4188416a47269f8433f70502abe98
- https://git.kernel.org/stable/c/0c3e6288da650d1ec911a259c77bc2d88e498603
- https://git.kernel.org/stable/c/cdf01c807e974048c43c7fd3ca574f6086a57906
- https://git.kernel.org/stable/c/2de8eec8afb75792440b8900a01d52b8f6742fd1
- https://git.kernel.org/stable/c/7480aeff0093d8c54377553ec6b31110bea37b4d
- https://git.kernel.org/stable/c/8cf0a1bc12870d148ae830a4ba88cfdf0e879cee
Frequently Asked Questions
What is the severity of CVE-2022-49890?
The CVE-2022-49890 vulnerability has a low severity rating due to the specific conditions needed for exploitation.
How do I fix CVE-2022-49890?
To mitigate CVE-2022-49890, update to the latest version of the Linux Kernel where the vulnerability has been patched.
What is the impact of CVE-2022-49890?
CVE-2022-49890 could potentially lead to a memory leak in the Linux kernel during the execution of specific operations.
Is CVE-2022-49890 remotely exploitable?
CVE-2022-49890 is not considered to be remotely exploitable as it requires local access to the affected system.
What versions of the Linux Kernel are affected by CVE-2022-49890?
CVE-2022-49890 affects multiple versions of the Linux Kernel prior to the security patch release.
- agent/title
- agent/references
- agent/description
- agent/first-publish-date
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/author
- agent/source
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/remedy
- agent/softwarecombine
- agent/event
- collector/nvd-api
- source/NVD
- vendor/linux
- canonical/linux kernel
- version/linux kernel/4.14
- version/linux kernel/4.15
- version/linux kernel/4.20
- version/linux kernel/5.5
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.1-rc1
- version/linux kernel/6.1-rc2
- version/linux kernel/6.1-rc3