CVE-2025-21672: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: afs: Fix merge preference rule failure condition syzbot reported a lock held when returning to userspace[1]. This is because if argc is less than 0 and the function returns directly, the held inode lock is not released. Fix this by store the error in ret and jump to done to clean up instead of returning directly. [dh: Modified Lizhi Xu's original patch to make it honour the error code from afs_split_string()] [1] WARNING: lock held when returning to user space! 6.13.0-rc3-syzkaller-00209-g499551201b5f #0 Not tainted ------------------------------------------------ syz-executor133/5823 is leaving the kernel with locks still held! 1 lock held by syz-executor133/5823: #0: ffff888071cffc00 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] #0: ffff888071cffc00 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: afs_proc_addr_prefs_write+0x2bb/0x14e0 fs/afs/addr_prefs.c:388
AI Analysis
Technical Summary
CVE-2025-21672 is a vulnerability identified in the Linux kernel, specifically within the AFS (Andrew File System) module's address preferences writing function (afs_proc_addr_prefs_write). The issue arises from improper lock management when an error condition occurs. If the argument count (argc) is less than zero, the function returns prematurely without releasing a held inode lock (i_mutex_key). This results in the kernel returning to userspace while still holding a lock, which is a critical kernel programming error. The vulnerability was discovered through syzbot, an automated kernel fuzzing tool, which reported a warning indicating that a lock was held when returning to userspace. The root cause is that the error path does not properly clean up by releasing the inode lock, leading to a potential deadlock or kernel instability. The fix involves modifying the error handling to store the error code and jump to a cleanup section that releases the lock before returning, ensuring proper lock release even in error conditions. This patch also respects the error code returned by afs_split_string(), improving error handling robustness. The vulnerability affects specific Linux kernel versions identified by commit hashes and is relevant to systems using the AFS filesystem module. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the affected AFS module versions. The improper lock release can lead to kernel instability, including potential deadlocks or system hangs, which may cause denial of service (DoS) conditions. Organizations relying on Linux servers for critical infrastructure, file sharing, or network services using AFS could experience service disruptions. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting system instability can impact availability and operational continuity. Given the widespread use of Linux in European data centers, cloud environments, and enterprise servers, the vulnerability could affect a broad range of sectors including finance, telecommunications, government, and academia. The absence of known exploits reduces immediate risk, but the vulnerability's nature means that attackers or malware could potentially exploit it to cause DoS or disrupt services, especially in environments where AFS is actively used.
Mitigation Recommendations
European organizations should promptly apply the Linux kernel patches that address CVE-2025-21672 once they are available from their Linux distribution vendors. Since the vulnerability is in the kernel's AFS module, organizations should audit their systems to identify if AFS is in use and if the affected kernel versions are deployed. For systems not using AFS, the risk is minimal, but kernel updates are still recommended. Additionally, organizations should implement monitoring for kernel warnings or logs indicating lock-related errors, which could signal attempts to trigger this vulnerability. In environments where immediate patching is not feasible, consider isolating affected systems or limiting access to reduce exposure. Regular kernel updates and adherence to vendor security advisories are critical. Finally, testing kernel updates in staging environments before production deployment can prevent unexpected disruptions.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Poland, Italy, Spain
CVE-2025-21672: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: afs: Fix merge preference rule failure condition syzbot reported a lock held when returning to userspace[1]. This is because if argc is less than 0 and the function returns directly, the held inode lock is not released. Fix this by store the error in ret and jump to done to clean up instead of returning directly. [dh: Modified Lizhi Xu's original patch to make it honour the error code from afs_split_string()] [1] WARNING: lock held when returning to user space! 6.13.0-rc3-syzkaller-00209-g499551201b5f #0 Not tainted ------------------------------------------------ syz-executor133/5823 is leaving the kernel with locks still held! 1 lock held by syz-executor133/5823: #0: ffff888071cffc00 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] #0: ffff888071cffc00 (&sb->s_type->i_mutex_key#9){++++}-{4:4}, at: afs_proc_addr_prefs_write+0x2bb/0x14e0 fs/afs/addr_prefs.c:388
AI-Powered Analysis
Technical Analysis
CVE-2025-21672 is a vulnerability identified in the Linux kernel, specifically within the AFS (Andrew File System) module's address preferences writing function (afs_proc_addr_prefs_write). The issue arises from improper lock management when an error condition occurs. If the argument count (argc) is less than zero, the function returns prematurely without releasing a held inode lock (i_mutex_key). This results in the kernel returning to userspace while still holding a lock, which is a critical kernel programming error. The vulnerability was discovered through syzbot, an automated kernel fuzzing tool, which reported a warning indicating that a lock was held when returning to userspace. The root cause is that the error path does not properly clean up by releasing the inode lock, leading to a potential deadlock or kernel instability. The fix involves modifying the error handling to store the error code and jump to a cleanup section that releases the lock before returning, ensuring proper lock release even in error conditions. This patch also respects the error code returned by afs_split_string(), improving error handling robustness. The vulnerability affects specific Linux kernel versions identified by commit hashes and is relevant to systems using the AFS filesystem module. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the affected AFS module versions. The improper lock release can lead to kernel instability, including potential deadlocks or system hangs, which may cause denial of service (DoS) conditions. Organizations relying on Linux servers for critical infrastructure, file sharing, or network services using AFS could experience service disruptions. While this vulnerability does not directly lead to privilege escalation or data leakage, the resulting system instability can impact availability and operational continuity. Given the widespread use of Linux in European data centers, cloud environments, and enterprise servers, the vulnerability could affect a broad range of sectors including finance, telecommunications, government, and academia. The absence of known exploits reduces immediate risk, but the vulnerability's nature means that attackers or malware could potentially exploit it to cause DoS or disrupt services, especially in environments where AFS is actively used.
Mitigation Recommendations
European organizations should promptly apply the Linux kernel patches that address CVE-2025-21672 once they are available from their Linux distribution vendors. Since the vulnerability is in the kernel's AFS module, organizations should audit their systems to identify if AFS is in use and if the affected kernel versions are deployed. For systems not using AFS, the risk is minimal, but kernel updates are still recommended. Additionally, organizations should implement monitoring for kernel warnings or logs indicating lock-related errors, which could signal attempts to trigger this vulnerability. In environments where immediate patching is not feasible, consider isolating affected systems or limiting access to reduce exposure. Regular kernel updates and adherence to vendor security advisories are critical. Finally, testing kernel updates in staging environments before production deployment can prevent unexpected disruptions.
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-12-29T08:45:45.736Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9834c4522896dcbe97b0
Added to database: 5/21/2025, 9:09:08 AM
Last enriched: 6/30/2025, 4:57:54 PM
Last updated: 7/31/2025, 9:23:30 PM
Views: 13
Related Threats
CVE-2025-55164: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in helmetjs content-security-policy-parser
HighCVE-2025-3089: CWE-639 Authorization Bypass Through User-Controlled Key in ServiceNow ServiceNow AI Platform
MediumCVE-2025-54864: CWE-306: Missing Authentication for Critical Function in NixOS hydra
MediumCVE-2025-54800: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in NixOS hydra
HighCVE-2025-8452: CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory in Brother Industries, Ltd HL-L8260CDN
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.