CVE-2022-48924: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: thermal: int340x: fix memory leak in int3400_notify() It is easy to hit the below memory leaks in my TigerLake platform: unreferenced object 0xffff927c8b91dbc0 (size 32): comm "kworker/0:2", pid 112, jiffies 4294893323 (age 83.604s) hex dump (first 32 bytes): 4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65 NAME=INT3400 The 72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 rmal.kkkkkkkkkk. backtrace: [<ffffffff9c502c3e>] __kmalloc_track_caller+0x2fe/0x4a0 [<ffffffff9c7b7c15>] kvasprintf+0x65/0xd0 [<ffffffff9c7b7d6e>] kasprintf+0x4e/0x70 [<ffffffffc04cb662>] int3400_notify+0x82/0x120 [int3400_thermal] [<ffffffff9c8b7358>] acpi_ev_notify_dispatch+0x54/0x71 [<ffffffff9c88f1a7>] acpi_os_execute_deferred+0x17/0x30 [<ffffffff9c2c2c0a>] process_one_work+0x21a/0x3f0 [<ffffffff9c2c2e2a>] worker_thread+0x4a/0x3b0 [<ffffffff9c2cb4dd>] kthread+0xfd/0x130 [<ffffffff9c201c1f>] ret_from_fork+0x1f/0x30 Fix it by calling kfree() accordingly.
AI Analysis
Technical Summary
CVE-2022-48924 is a vulnerability identified in the Linux kernel specifically related to the thermal management driver int340x, which handles ACPI thermal notifications on Intel TigerLake platforms. The issue is a memory leak in the function int3400_notify(), where allocated memory is not properly freed, leading to unreferenced objects accumulating over time. The vulnerability manifests as a failure to call kfree() on allocated memory, causing a leak of 32 bytes per notification event. This leak occurs during the processing of ACPI thermal events dispatched by the kernel worker threads. The backtrace indicates the leak happens in the kernel's memory allocation tracking and string formatting functions (kvasprintf and kasprintf) used within int3400_notify(). Although the leak size per event is small, continuous triggering can lead to significant memory consumption, potentially degrading system performance or causing resource exhaustion. The vulnerability affects Linux kernel versions identified by the commit hash 38e44da591303d08b0d965a033e11ade284999d0, which corresponds to a specific kernel release series. The fix involves proper invocation of kfree() to release allocated memory, preventing the leak. There are no known exploits in the wild, and no CVSS score has been assigned yet. This vulnerability is primarily a resource management flaw rather than a direct code execution or privilege escalation issue.
Potential Impact
For European organizations, the impact of CVE-2022-48924 is primarily related to system stability and availability rather than confidentiality or integrity. Systems running affected Linux kernel versions on Intel TigerLake hardware could experience gradual memory exhaustion due to the leak, leading to degraded performance or potential crashes in critical infrastructure or servers. This could affect data centers, cloud providers, and enterprises relying on Linux-based servers or workstations with TigerLake processors. While the vulnerability does not directly enable remote code execution or privilege escalation, the resulting denial of service through resource depletion could disrupt business operations, especially in environments with high thermal event frequency or long uptimes. Organizations with large-scale deployments of Linux on TigerLake platforms should be aware of the risk of performance degradation and plan for timely patching to maintain service reliability.
Mitigation Recommendations
To mitigate CVE-2022-48924, European organizations should: 1) Identify and inventory Linux systems running affected kernel versions on Intel TigerLake hardware. 2) Apply the official Linux kernel patches that fix the memory leak by ensuring kfree() is called appropriately in int3400_notify(). If vendor-specific distributions are used, monitor for vendor-provided updates addressing this issue. 3) Monitor system memory usage and kernel logs for signs of memory leaks or thermal event anomalies, especially on systems with prolonged uptimes. 4) Implement proactive system reboots or memory management strategies as interim measures if patching is delayed. 5) Engage with hardware and OS vendors to confirm the deployment of fixes and validate system stability post-update. 6) Consider disabling or limiting thermal event notifications if feasible and safe, as a temporary workaround to reduce leak triggers. These steps go beyond generic advice by focusing on hardware-specific identification, monitoring, and vendor coordination.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Ireland, Belgium, Italy
CVE-2022-48924: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: thermal: int340x: fix memory leak in int3400_notify() It is easy to hit the below memory leaks in my TigerLake platform: unreferenced object 0xffff927c8b91dbc0 (size 32): comm "kworker/0:2", pid 112, jiffies 4294893323 (age 83.604s) hex dump (first 32 bytes): 4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65 NAME=INT3400 The 72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 rmal.kkkkkkkkkk. backtrace: [<ffffffff9c502c3e>] __kmalloc_track_caller+0x2fe/0x4a0 [<ffffffff9c7b7c15>] kvasprintf+0x65/0xd0 [<ffffffff9c7b7d6e>] kasprintf+0x4e/0x70 [<ffffffffc04cb662>] int3400_notify+0x82/0x120 [int3400_thermal] [<ffffffff9c8b7358>] acpi_ev_notify_dispatch+0x54/0x71 [<ffffffff9c88f1a7>] acpi_os_execute_deferred+0x17/0x30 [<ffffffff9c2c2c0a>] process_one_work+0x21a/0x3f0 [<ffffffff9c2c2e2a>] worker_thread+0x4a/0x3b0 [<ffffffff9c2cb4dd>] kthread+0xfd/0x130 [<ffffffff9c201c1f>] ret_from_fork+0x1f/0x30 Fix it by calling kfree() accordingly.
AI-Powered Analysis
Technical Analysis
CVE-2022-48924 is a vulnerability identified in the Linux kernel specifically related to the thermal management driver int340x, which handles ACPI thermal notifications on Intel TigerLake platforms. The issue is a memory leak in the function int3400_notify(), where allocated memory is not properly freed, leading to unreferenced objects accumulating over time. The vulnerability manifests as a failure to call kfree() on allocated memory, causing a leak of 32 bytes per notification event. This leak occurs during the processing of ACPI thermal events dispatched by the kernel worker threads. The backtrace indicates the leak happens in the kernel's memory allocation tracking and string formatting functions (kvasprintf and kasprintf) used within int3400_notify(). Although the leak size per event is small, continuous triggering can lead to significant memory consumption, potentially degrading system performance or causing resource exhaustion. The vulnerability affects Linux kernel versions identified by the commit hash 38e44da591303d08b0d965a033e11ade284999d0, which corresponds to a specific kernel release series. The fix involves proper invocation of kfree() to release allocated memory, preventing the leak. There are no known exploits in the wild, and no CVSS score has been assigned yet. This vulnerability is primarily a resource management flaw rather than a direct code execution or privilege escalation issue.
Potential Impact
For European organizations, the impact of CVE-2022-48924 is primarily related to system stability and availability rather than confidentiality or integrity. Systems running affected Linux kernel versions on Intel TigerLake hardware could experience gradual memory exhaustion due to the leak, leading to degraded performance or potential crashes in critical infrastructure or servers. This could affect data centers, cloud providers, and enterprises relying on Linux-based servers or workstations with TigerLake processors. While the vulnerability does not directly enable remote code execution or privilege escalation, the resulting denial of service through resource depletion could disrupt business operations, especially in environments with high thermal event frequency or long uptimes. Organizations with large-scale deployments of Linux on TigerLake platforms should be aware of the risk of performance degradation and plan for timely patching to maintain service reliability.
Mitigation Recommendations
To mitigate CVE-2022-48924, European organizations should: 1) Identify and inventory Linux systems running affected kernel versions on Intel TigerLake hardware. 2) Apply the official Linux kernel patches that fix the memory leak by ensuring kfree() is called appropriately in int3400_notify(). If vendor-specific distributions are used, monitor for vendor-provided updates addressing this issue. 3) Monitor system memory usage and kernel logs for signs of memory leaks or thermal event anomalies, especially on systems with prolonged uptimes. 4) Implement proactive system reboots or memory management strategies as interim measures if patching is delayed. 5) Engage with hardware and OS vendors to confirm the deployment of fixes and validate system stability post-update. 6) Consider disabling or limiting thermal event notifications if feasible and safe, as a temporary workaround to reduce leak triggers. These steps go beyond generic advice by focusing on hardware-specific identification, monitoring, and vendor coordination.
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
- 2024-08-21T06:06:23.296Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d982fc4522896dcbe65f4
Added to database: 5/21/2025, 9:09:03 AM
Last enriched: 6/30/2025, 11:42:52 PM
Last updated: 7/29/2025, 12:30:37 AM
Views: 10
Related Threats
CVE-2025-9022: SQL Injection in SourceCodester Online Bank Management System
MediumCVE-2025-9021: SQL Injection in SourceCodester Online Bank Management System
MediumCVE-2025-9020: Use After Free in PX4 PX4-Autopilot
LowCVE-2025-8604: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in wptb WP Table Builder – WordPress Table Plugin
MediumCVE-2025-9016: Uncontrolled Search Path in Mechrevo Control Center GX V2
HighActions
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.