CVE-2021-47412: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: block: don't call rq_qos_ops->done_bio if the bio isn't tracked rq_qos framework is only applied on request based driver, so: 1) rq_qos_done_bio() needn't to be called for bio based driver 2) rq_qos_done_bio() needn't to be called for bio which isn't tracked, such as bios ended from error handling code. Especially in bio_endio(): 1) request queue is referred via bio->bi_bdev->bd_disk->queue, which may be gone since request queue refcount may not be held in above two cases 2) q->rq_qos may be freed in blk_cleanup_queue() when calling into __rq_qos_done_bio() Fix the potential kernel panic by not calling rq_qos_ops->done_bio if the bio isn't tracked. This way is safe because both ioc_rqos_done_bio() and blkcg_iolatency_done_bio() are nop if the bio isn't tracked.
AI Analysis
Technical Summary
CVE-2021-47412 is a vulnerability identified in the Linux kernel's block layer, specifically related to the request queue quality of service (rq_qos) framework. The issue arises because the rq_qos_done_bio() function is called for block I/O (bio) operations that are not tracked by the rq_qos framework. The rq_qos framework is designed to manage request-based drivers, but bio-based drivers or bios that are not tracked (such as those ended due to error handling) should not invoke rq_qos_done_bio(). The vulnerability occurs because in bio_endio(), the request queue is accessed via bio->bi_bdev->bd_disk->queue without ensuring that the request queue's reference count is held, which can lead to a use-after-free or dereferencing a freed pointer. Additionally, the rq_qos structure may have been freed during blk_cleanup_queue(), causing rq_qos_ops->done_bio to be called on a freed object. This can result in a kernel panic, leading to a denial of service (DoS) condition. The fix involves adding checks to ensure rq_qos_ops->done_bio is only called if the bio is tracked, preventing invalid memory access and stabilizing kernel behavior. The vulnerability does not appear to have known exploits in the wild and affects Linux kernel versions identified by the commit hash 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2. No CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of denial of service through kernel panics on affected Linux systems. Since Linux is widely used in servers, cloud infrastructure, and embedded devices across Europe, exploitation could disrupt critical services, including web hosting, database operations, and network infrastructure. Although this vulnerability does not directly lead to privilege escalation or data leakage, the resulting system crashes could cause significant operational downtime and potential data loss if systems are not properly configured with redundancy or failover mechanisms. Organizations relying on Linux-based storage or block device drivers are particularly at risk. The absence of known exploits suggests that the threat is currently low, but unpatched systems remain vulnerable to accidental or malicious triggering of the kernel panic. This could impact sectors such as finance, telecommunications, government, and critical infrastructure within Europe, where Linux adoption is high and service availability is paramount.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should promptly apply the official Linux kernel patches that address CVE-2021-47412. Since the issue is related to kernel internals, updating to a fixed kernel version is the most effective measure. Organizations should: 1) Identify all Linux systems running affected kernel versions, especially those handling block devices or storage drivers. 2) Test and deploy updated kernels from trusted sources or vendor distributions that include the fix. 3) Implement robust monitoring for kernel panics or unusual system crashes that could indicate attempted exploitation. 4) Use kernel live patching solutions where available to minimize downtime during patch deployment. 5) Ensure backup and disaster recovery plans are in place to handle potential service interruptions. 6) Limit access to systems with block device drivers to trusted users and processes to reduce the risk of accidental triggering. 7) Engage with Linux distribution vendors for timely security updates and advisories. These steps go beyond generic advice by emphasizing proactive detection, controlled patch rollout, and operational continuity planning specific to kernel-level vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2021-47412: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: block: don't call rq_qos_ops->done_bio if the bio isn't tracked rq_qos framework is only applied on request based driver, so: 1) rq_qos_done_bio() needn't to be called for bio based driver 2) rq_qos_done_bio() needn't to be called for bio which isn't tracked, such as bios ended from error handling code. Especially in bio_endio(): 1) request queue is referred via bio->bi_bdev->bd_disk->queue, which may be gone since request queue refcount may not be held in above two cases 2) q->rq_qos may be freed in blk_cleanup_queue() when calling into __rq_qos_done_bio() Fix the potential kernel panic by not calling rq_qos_ops->done_bio if the bio isn't tracked. This way is safe because both ioc_rqos_done_bio() and blkcg_iolatency_done_bio() are nop if the bio isn't tracked.
AI-Powered Analysis
Technical Analysis
CVE-2021-47412 is a vulnerability identified in the Linux kernel's block layer, specifically related to the request queue quality of service (rq_qos) framework. The issue arises because the rq_qos_done_bio() function is called for block I/O (bio) operations that are not tracked by the rq_qos framework. The rq_qos framework is designed to manage request-based drivers, but bio-based drivers or bios that are not tracked (such as those ended due to error handling) should not invoke rq_qos_done_bio(). The vulnerability occurs because in bio_endio(), the request queue is accessed via bio->bi_bdev->bd_disk->queue without ensuring that the request queue's reference count is held, which can lead to a use-after-free or dereferencing a freed pointer. Additionally, the rq_qos structure may have been freed during blk_cleanup_queue(), causing rq_qos_ops->done_bio to be called on a freed object. This can result in a kernel panic, leading to a denial of service (DoS) condition. The fix involves adding checks to ensure rq_qos_ops->done_bio is only called if the bio is tracked, preventing invalid memory access and stabilizing kernel behavior. The vulnerability does not appear to have known exploits in the wild and affects Linux kernel versions identified by the commit hash 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2. No CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability primarily poses a risk of denial of service through kernel panics on affected Linux systems. Since Linux is widely used in servers, cloud infrastructure, and embedded devices across Europe, exploitation could disrupt critical services, including web hosting, database operations, and network infrastructure. Although this vulnerability does not directly lead to privilege escalation or data leakage, the resulting system crashes could cause significant operational downtime and potential data loss if systems are not properly configured with redundancy or failover mechanisms. Organizations relying on Linux-based storage or block device drivers are particularly at risk. The absence of known exploits suggests that the threat is currently low, but unpatched systems remain vulnerable to accidental or malicious triggering of the kernel panic. This could impact sectors such as finance, telecommunications, government, and critical infrastructure within Europe, where Linux adoption is high and service availability is paramount.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should promptly apply the official Linux kernel patches that address CVE-2021-47412. Since the issue is related to kernel internals, updating to a fixed kernel version is the most effective measure. Organizations should: 1) Identify all Linux systems running affected kernel versions, especially those handling block devices or storage drivers. 2) Test and deploy updated kernels from trusted sources or vendor distributions that include the fix. 3) Implement robust monitoring for kernel panics or unusual system crashes that could indicate attempted exploitation. 4) Use kernel live patching solutions where available to minimize downtime during patch deployment. 5) Ensure backup and disaster recovery plans are in place to handle potential service interruptions. 6) Limit access to systems with block device drivers to trusted users and processes to reduce the risk of accidental triggering. 7) Engage with Linux distribution vendors for timely security updates and advisories. These steps go beyond generic advice by emphasizing proactive detection, controlled patch rollout, and operational continuity planning specific to kernel-level vulnerabilities.
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-05-21T14:58:30.817Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9833c4522896dcbe9078
Added to database: 5/21/2025, 9:09:07 AM
Last enriched: 6/30/2025, 12:40:00 PM
Last updated: 8/13/2025, 2:24:59 AM
Views: 15
Related Threats
CVE-2025-52621: CWE-346 Origin Validation Error in HCL Software BigFix SaaS Remediate
MediumCVE-2025-52620: CWE-20 Improper Input Validation in HCL Software BigFix SaaS Remediate
MediumCVE-2025-52619: CWE-209 Generation of Error Message Containing Sensitive Information in HCL Software BigFix SaaS Remediate
MediumCVE-2025-52618: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in HCL Software BigFix SaaS Remediate
MediumCVE-2025-43201: An app may be able to unexpectedly leak a user's credentials in Apple Apple Music Classical for Android
UnknownActions
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.