CVE-2022-49256: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: watch_queue: Actually free the watch free_watch() does everything barring actually freeing the watch object. Fix this by adding the missing kfree. kmemleak produces a report something like the following. Note that as an address can be seen in the first word, the watch would appear to have gone through call_rcu(). BUG: memory leak unreferenced object 0xffff88810ce4a200 (size 96): comm "syz-executor352", pid 3605, jiffies 4294947473 (age 13.720s) hex dump (first 32 bytes): e0 82 48 0d 81 88 ff ff 00 00 00 00 00 00 00 00 ..H............. 80 a2 e4 0c 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff8214e6cc>] kmalloc include/linux/slab.h:581 [inline] [<ffffffff8214e6cc>] kzalloc include/linux/slab.h:714 [inline] [<ffffffff8214e6cc>] keyctl_watch_key+0xec/0x2e0 security/keys/keyctl.c:1800 [<ffffffff8214ec84>] __do_sys_keyctl+0x3c4/0x490 security/keys/keyctl.c:2016 [<ffffffff84493a25>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff84493a25>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [<ffffffff84600068>] entry_SYSCALL_64_after_hwframe+0x44/0xae
AI Analysis
Technical Summary
CVE-2022-49256 is a vulnerability identified in the Linux kernel related to improper memory management in the watch_queue subsystem, specifically in the function free_watch(). The vulnerability arises because free_watch() performs all necessary cleanup operations except for actually freeing the allocated memory for the watch object, missing a call to kfree(). This omission results in a memory leak where allocated memory is not released back to the system. The issue was detected through reports generated by kmemleak, a kernel memory leak detector, which showed unreferenced objects persisting in memory. The backtrace indicates the leak occurs during key management operations, particularly within keyctl_watch_key and __do_sys_keyctl functions. Although this vulnerability does not directly lead to code execution or privilege escalation, the memory leak can cause gradual resource exhaustion, potentially degrading system performance or stability over time. The vulnerability affects specific Linux kernel versions identified by commit hashes, and no known exploits are currently reported in the wild. The patch involves adding the missing kfree() call to properly free the watch object and prevent the leak.
Potential Impact
For European organizations relying on Linux-based systems, this vulnerability could lead to gradual memory exhaustion on critical servers or infrastructure devices, especially those with long uptimes or high usage of key management features. While the vulnerability does not allow direct compromise of confidentiality or integrity, the resulting memory leak can cause system instability, degraded performance, or unexpected crashes, potentially impacting availability of services. This is particularly relevant for data centers, cloud providers, and enterprises running Linux in production environments. Systems involved in security-sensitive operations using keyctl or related key management APIs might be more exposed to the leak. Over time, unmitigated memory leaks can increase operational costs due to increased maintenance and downtime. However, since exploitation does not require user interaction or authentication, the risk of unnoticed degradation is higher. The absence of known exploits reduces immediate threat but does not eliminate the risk of future exploitation or impact from resource exhaustion.
Mitigation Recommendations
European organizations should promptly apply the official Linux kernel patches that include the fix for CVE-2022-49256, ensuring the missing kfree() call is added to free_watch(). For environments where immediate patching is challenging, monitoring tools should be deployed to track memory usage trends and detect abnormal memory growth indicative of leaks. Administrators should audit usage of key management APIs such as keyctl to identify systems with higher exposure. Implementing kernel memory leak detection tools like kmemleak in testing and staging environments can help identify similar issues proactively. Additionally, organizations should maintain strict update policies for Linux kernels and related components, leveraging vendor-provided security advisories. For critical infrastructure, consider scheduled reboots or memory cleanup procedures as temporary mitigations until patches are applied. Finally, ensure robust logging and alerting mechanisms are in place to detect system instability or crashes potentially related to memory exhaustion.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2022-49256: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: watch_queue: Actually free the watch free_watch() does everything barring actually freeing the watch object. Fix this by adding the missing kfree. kmemleak produces a report something like the following. Note that as an address can be seen in the first word, the watch would appear to have gone through call_rcu(). BUG: memory leak unreferenced object 0xffff88810ce4a200 (size 96): comm "syz-executor352", pid 3605, jiffies 4294947473 (age 13.720s) hex dump (first 32 bytes): e0 82 48 0d 81 88 ff ff 00 00 00 00 00 00 00 00 ..H............. 80 a2 e4 0c 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff8214e6cc>] kmalloc include/linux/slab.h:581 [inline] [<ffffffff8214e6cc>] kzalloc include/linux/slab.h:714 [inline] [<ffffffff8214e6cc>] keyctl_watch_key+0xec/0x2e0 security/keys/keyctl.c:1800 [<ffffffff8214ec84>] __do_sys_keyctl+0x3c4/0x490 security/keys/keyctl.c:2016 [<ffffffff84493a25>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff84493a25>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [<ffffffff84600068>] entry_SYSCALL_64_after_hwframe+0x44/0xae
AI-Powered Analysis
Technical Analysis
CVE-2022-49256 is a vulnerability identified in the Linux kernel related to improper memory management in the watch_queue subsystem, specifically in the function free_watch(). The vulnerability arises because free_watch() performs all necessary cleanup operations except for actually freeing the allocated memory for the watch object, missing a call to kfree(). This omission results in a memory leak where allocated memory is not released back to the system. The issue was detected through reports generated by kmemleak, a kernel memory leak detector, which showed unreferenced objects persisting in memory. The backtrace indicates the leak occurs during key management operations, particularly within keyctl_watch_key and __do_sys_keyctl functions. Although this vulnerability does not directly lead to code execution or privilege escalation, the memory leak can cause gradual resource exhaustion, potentially degrading system performance or stability over time. The vulnerability affects specific Linux kernel versions identified by commit hashes, and no known exploits are currently reported in the wild. The patch involves adding the missing kfree() call to properly free the watch object and prevent the leak.
Potential Impact
For European organizations relying on Linux-based systems, this vulnerability could lead to gradual memory exhaustion on critical servers or infrastructure devices, especially those with long uptimes or high usage of key management features. While the vulnerability does not allow direct compromise of confidentiality or integrity, the resulting memory leak can cause system instability, degraded performance, or unexpected crashes, potentially impacting availability of services. This is particularly relevant for data centers, cloud providers, and enterprises running Linux in production environments. Systems involved in security-sensitive operations using keyctl or related key management APIs might be more exposed to the leak. Over time, unmitigated memory leaks can increase operational costs due to increased maintenance and downtime. However, since exploitation does not require user interaction or authentication, the risk of unnoticed degradation is higher. The absence of known exploits reduces immediate threat but does not eliminate the risk of future exploitation or impact from resource exhaustion.
Mitigation Recommendations
European organizations should promptly apply the official Linux kernel patches that include the fix for CVE-2022-49256, ensuring the missing kfree() call is added to free_watch(). For environments where immediate patching is challenging, monitoring tools should be deployed to track memory usage trends and detect abnormal memory growth indicative of leaks. Administrators should audit usage of key management APIs such as keyctl to identify systems with higher exposure. Implementing kernel memory leak detection tools like kmemleak in testing and staging environments can help identify similar issues proactively. Additionally, organizations should maintain strict update policies for Linux kernels and related components, leveraging vendor-provided security advisories. For critical infrastructure, consider scheduled reboots or memory cleanup procedures as temporary mitigations until patches are applied. Finally, ensure robust logging and alerting mechanisms are in place to detect system instability or crashes potentially related to memory exhaustion.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-02-26T01:49:39.296Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982dc4522896dcbe545a
Added to database: 5/21/2025, 9:09:01 AM
Last enriched: 6/30/2025, 4:55:58 AM
Last updated: 7/31/2025, 4:00:07 AM
Views: 13
Related Threats
CVE-2025-8293: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Theerawat Patthawee Intl DateTime Calendar
MediumCVE-2025-7686: CWE-352 Cross-Site Request Forgery (CSRF) in lmyoaoa weichuncai(WP伪春菜)
MediumCVE-2025-7684: CWE-352 Cross-Site Request Forgery (CSRF) in remysharp Last.fm Recent Album Artwork
MediumCVE-2025-7683: CWE-352 Cross-Site Request Forgery (CSRF) in janyksteenbeek LatestCheckins
MediumCVE-2025-7668: CWE-352 Cross-Site Request Forgery (CSRF) in timothyja Linux Promotional Plugin
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.