CVE-2022-49890
published 2025-05-01CVE-2022-49890: In the Linux kernel, the following vulnerability has been resolved: capabilities: fix potential memleak on error path from vfs_getxattr_alloc() In…
PriorityP417medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.0th percentile
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]
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.8-1 (bookworm) | linux 6.0.8-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < 6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85 | 6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85 |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < 90577bcc01c4188416a47269f8433f70502abe98 | 90577bcc01c4188416a47269f8433f70502abe98 |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < 0c3e6288da650d1ec911a259c77bc2d88e498603 | 0c3e6288da650d1ec911a259c77bc2d88e498603 |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < cdf01c807e974048c43c7fd3ca574f6086a57906 | cdf01c807e974048c43c7fd3ca574f6086a57906 |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < 2de8eec8afb75792440b8900a01d52b8f6742fd1 | 2de8eec8afb75792440b8900a01d52b8f6742fd1 |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < 7480aeff0093d8c54377553ec6b31110bea37b4d | 7480aeff0093d8c54377553ec6b31110bea37b4d |
| linux | linux | >= 8db6c34f1dbc8e06aa016a9b829b06902c3e1340 < 8cf0a1bc12870d148ae830a4ba88cfdf0e879cee | 8cf0a1bc12870d148ae830a4ba88cfdf0e879cee |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.8-1 | 6.0.8-1 |
| linux | linux_kernel | >= 0 < 6.0.8-1 | 6.0.8-1 |
| linux | linux_kernel | >= 0 < 6.0.8-1 | 6.0.8-1 |
| linux | linux_kernel | >= 4.14 < 4.14.299 | 4.14.299 |
| linux | linux_kernel | >= 4.15 < 4.19.265 | 4.19.265 |
| linux | linux_kernel | >= 4.20 < 5.4.224 | 5.4.224 |
| linux | linux_kernel | >= 5.11 < 5.15.78 | 5.15.78 |
| linux | linux_kernel | >= 5.16 < 6.0.8 | 6.0.8 |
| linux | linux_kernel | >= 5.5 < 5.10.154 | 5.10.154 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-wxgf-7f8j-hr6j: In the Linux kernel, the following vulnerability has been resolved:
capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
In c
ghsa_unreviewed·2025-05-01
CVE-2022-49890 [MEDIUM] CWE-401 GHSA-wxgf-7f8j-hr6j: In the Linux kernel, the following vulnerability has been resolved:
capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
In c
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]
OSV
CVE-2022-49890: In the Linux kernel, the following vulnerability has been resolved: capabilities: fix potential memleak on error path from vfs_getxattr_alloc() In cap
osv·2025-05-01·CVSS 5.5
CVE-2022-49890 [MEDIUM] CVE-2022-49890: In the Linux kernel, the following vulnerability has been resolved: capabilities: fix potential memleak on error path from vfs_getxattr_alloc() In cap
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]
Red Hat
kernel: capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
vendor_redhat·2025-05-01·CVSS 5.5
CVE-2022-49890 [MEDIUM] CWE-401 kernel: capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
kernel: capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
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_
Debian
CVE-2022-49890: linux - In the Linux kernel, the following vulnerability has been resolved: capabilitie...
vendor_debian·2022·CVSS 5.5
CVE-2022-49890 [MEDIUM] CVE-2022-49890: linux - In the Linux kernel, the following vulnerability has been resolved: capabilitie...
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]
Scope: local
bookwor
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0c3e6288da650d1ec911a259c77bc2d88e498603https://git.kernel.org/stable/c/2de8eec8afb75792440b8900a01d52b8f6742fd1https://git.kernel.org/stable/c/6bb00eb21c0fbf18e5d3538c9ff0cf63fd0ace85https://git.kernel.org/stable/c/7480aeff0093d8c54377553ec6b31110bea37b4dhttps://git.kernel.org/stable/c/8cf0a1bc12870d148ae830a4ba88cfdf0e879ceehttps://git.kernel.org/stable/c/90577bcc01c4188416a47269f8433f70502abe98https://git.kernel.org/stable/c/cdf01c807e974048c43c7fd3ca574f6086a57906
2025-05-01
Published