Answer in brief
CVE-2021-47401 records a High severity (CVSS 7.1) vulnerability in ipack: ipoctal: fix stack information leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2021-47401 records a High severity (CVSS 7.1) vulnerability in ipack: ipoctal: fix stack information leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.15:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.15:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 3.5 | Not reported |
| Linux/Linuxgeneric | >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <acb96e782bad427ca4bb1bd94af660acd1462380 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <741ea2670e021350e54f491106bdaa22dc50e6a0 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <2725925982dc96a78069cd118ea3d66759bfdad7 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <829f13d6079cf7a2465522f39acb43033e9b320d || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <8657158a3b68c85234e6da3d8eae33d6183588b7 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <5f6a309a699675680df15d9b6d389114515b4426 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <0a9c36a2e06a249acbed64e8e0b84637c2ad7575 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <a89936cce87d60766a75732a9e7e25c51164f47c | acb96e782bad427ca4bb1bd94af660acd1462380, 741ea2670e021350e54f491106bdaa22dc50e6a0, 2725925982dc96a78069cd118ea3d66759bfdad7, 829f13d6079cf7a2465522f39acb43033e9b320d, 8657158a3b68c85234e6da3d8eae33d6183588b7, 5f6a309a699675680df15d9b6d389114515b4426, 0a9c36a2e06a249acbed64e8e0b84637c2ad7575, a89936cce87d60766a75732a9e7e25c51164f47c |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix stack information leak The tty driver name is used also after registering the driver and must specifically not be allocated on the stack to avoid leaking information to user space (or triggering an oops). Drivers should not try to encode topology information in the tty device name but this one snuck in through staging without anyone noticing and another driver has since copied this malpractice. Fixing the ABI is a separate issue, but this at least plugs the security hole.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.15:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.15:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:5.15:rc3:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 3.5 | Not reported |
| Linux/Linuxgeneric | >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <acb96e782bad427ca4bb1bd94af660acd1462380 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <741ea2670e021350e54f491106bdaa22dc50e6a0 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <2725925982dc96a78069cd118ea3d66759bfdad7 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <829f13d6079cf7a2465522f39acb43033e9b320d || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <8657158a3b68c85234e6da3d8eae33d6183588b7 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <5f6a309a699675680df15d9b6d389114515b4426 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <0a9c36a2e06a249acbed64e8e0b84637c2ad7575 || >=ba4dc61fe8c545a5d6a68b63616776556b771f51 <a89936cce87d60766a75732a9e7e25c51164f47c | acb96e782bad427ca4bb1bd94af660acd1462380, 741ea2670e021350e54f491106bdaa22dc50e6a0, 2725925982dc96a78069cd118ea3d66759bfdad7, 829f13d6079cf7a2465522f39acb43033e9b320d, 8657158a3b68c85234e6da3d8eae33d6183588b7, 5f6a309a699675680df15d9b6d389114515b4426, 0a9c36a2e06a249acbed64e8e0b84637c2ad7575, a89936cce87d60766a75732a9e7e25c51164f47c |
Published upstream
May 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix stack information leak The tty driver name is used also after registering the driver and must specifically not be allocated on the stack to avoid leaking information to user space (or triggering an oops). Drivers should not try to encode topology information in the tty device name but this one snuck in through staging without anyone noticing and another driver has since copied this malpractice. Fixing the ABI is a separate issue, but this at least plugs the security hole.
Quoted source text, attributed separately from HOL analysis.