Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2022-49807: Vulnerability in Linux Linux

0
Medium
VulnerabilityCVE-2022-49807cvecve-2022-49807
Published: Thu May 01 2025 (05/01/2025, 14:09:33 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix a memory leak in nvmet_auth_set_key When changing dhchap secrets we need to release the old secrets as well. kmemleak complaint: -- unreferenced object 0xffff8c7f44ed8180 (size 64): comm "check", pid 7304, jiffies 4295686133 (age 72034.246s) hex dump (first 32 bytes): 44 48 48 43 2d 31 3a 30 30 3a 4c 64 4c 4f 64 71 DHHC-1:00:LdLOdq 79 56 69 67 77 48 55 32 6d 5a 59 4c 7a 35 59 38 yVigwHU2mZYLz5Y8 backtrace: [<00000000b6fc5071>] kstrdup+0x2e/0x60 [<00000000f0f4633f>] 0xffffffffc0e07ee6 [<0000000053006c05>] 0xffffffffc0dff783 [<00000000419ae922>] configfs_write_iter+0xb1/0x120 [<000000008183c424>] vfs_write+0x2be/0x3c0 [<000000009005a2a5>] ksys_write+0x5f/0xe0 [<00000000cd495c89>] do_syscall_64+0x38/0x90 [<00000000f2a84ac5>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

AI-Powered Analysis

AILast updated: 06/30/2025, 01:55:24 UTC

Technical Analysis

CVE-2022-49807 is a vulnerability identified in the Linux kernel specifically within the nvmet (NVMe target) subsystem. The issue is a memory leak occurring in the function nvmet_auth_set_key, which is responsible for managing authentication keys used in the NVMe over Fabrics (NVMe-oF) target implementation. The vulnerability arises when changing CHAP (Challenge-Handshake Authentication Protocol) secrets; the old secrets are not properly released, leading to unreleased memory allocations. This is evidenced by the kernel memory leak detector (kmemleak) reporting unreferenced objects related to the authentication keys. The backtrace shows the leak occurs during kernel string duplication (kstrdup) and configuration filesystem write operations (configfs_write_iter), indicating that the leak happens when configuration changes are applied to the nvmet subsystem. While the vulnerability does not directly allow code execution or privilege escalation, the memory leak can degrade system stability over time, potentially leading to resource exhaustion and denial of service (DoS) conditions on systems heavily utilizing NVMe-oF with CHAP authentication. The vulnerability has been fixed by ensuring that old secrets are properly freed when updated. No known exploits are reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, the impact of CVE-2022-49807 depends largely on their use of Linux systems as NVMe-oF targets, particularly in data centers, cloud providers, and enterprises with high-performance storage infrastructures. Organizations relying on NVMe-oF with CHAP authentication could experience gradual memory leaks leading to degraded performance or system crashes if the vulnerability is exploited or triggered by routine configuration changes. This could affect critical storage services, impacting availability and potentially causing downtime in environments where high availability is essential, such as financial institutions, healthcare providers, and industrial control systems. Although the vulnerability does not directly compromise confidentiality or integrity, the resulting denial of service could disrupt business operations and service delivery. The absence of known exploits reduces immediate risk, but the vulnerability should be addressed proactively to maintain system reliability.

Mitigation Recommendations

To mitigate CVE-2022-49807, European organizations should: 1) Apply the latest Linux kernel patches that address the memory leak in nvmet_auth_set_key as soon as they become available from trusted Linux distribution vendors or the upstream kernel. 2) Monitor systems running NVMe-oF targets with CHAP authentication for unusual memory usage patterns or kernel memory leak warnings using tools like kmemleak or system monitoring solutions. 3) Implement configuration management best practices to minimize frequent changes to CHAP secrets unless necessary, reducing the risk of triggering the leak. 4) Conduct regular kernel updates and testing in staging environments to ensure stability and security of storage subsystems. 5) Engage with Linux vendor support channels for guidance on backporting fixes if using long-term support kernels. 6) Consider additional monitoring and alerting on storage subsystem health to detect early signs of resource exhaustion or performance degradation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-05-01T14:05:17.225Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982cc4522896dcbe4c85

Added to database: 5/21/2025, 9:09:00 AM

Last enriched: 6/30/2025, 1:55:24 AM

Last updated: 10/16/2025, 3:13:25 PM

Views: 20

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats