CVE-2023-3006
Linux Kernel 6.1
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-3006 is a medium-severity Sensitive Information in Resource Not Removed Before Reuse (CWE-226) vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 17th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-43699
Vulnerability Data
A known cache speculation vulnerability, known as Branch History Injection (BHI) or Spectre-BHB, becomes actual again for the new hw AmpereOne. Spectre-BHB is similar to Spectre v2, except that malicious code uses the shared branch history (stored in the CPU…
more
Branch History Buffer, or BHB) to influence mispredicted branches within the victim's hardware context. Once that occurs, speculation caused by the mispredicted branches can cause cache allocation. This issue leads to obtaining information that should not be accessible.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 9 hardening rules · 4 OS baselines
V14.2.8V14.3.3V14.3.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Eradication of spilled information from contaminated systems mitigates the effects of improper removal of sensitive data before storage or transfer.
The control requires verified removal of sensitive data before media is made available at a reduced classification level, directly addressing improper removal prior to storage or transfer.
Retention policies enforce removal or sanitization of sensitive data before storage or transfer per regulatory requirements.
The explicit requirement to delete inaccurate/outdated PII implements proper removal of sensitive information before further storage or transfer.
The generate-on-demand-and-delete requirement enforces removal of sensitive information before storage or transfer, preventing improper retention.
Requires explicit removal of sensitive information prior to component transfer or disposal, reducing exposure from retained data.
Requiring sanitization of media prior to removal for off-site maintenance ensures sensitive information is removed before the resource is reused or accessed externally.
Procedures include sanitization, overwriting, and disposal requirements to remove sensitive data before media reuse or release.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Explicit example calls for removing confidential data (e.g., from process memory) after use, directly preventing reuse of uncleared resources.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; per the owner's explicit rule on labelling/classification controls, it has no direct preventing effect on a weakness unless and until another control (access, DLP, etc.) is configured to act on the resulting label.
Information-transfer rules can require sanitization of sensitive content before sharing.
A.5.34 only requires a privacy policy, procedures, assigned roles (e.g. privacy officer) and unspecified technical/organizational measures; it does not itself stop the improper retention of sensitive data before storage/transfer, so the weakness remains exploitable without depending on other controls.
Mandates secure disposal or re-use of equipment, covering media sanitization but not in-memory reuse.
Explicitly requires secure deletion of information before resources are reused or disposed.
A.8.11's masking/pseudonymization/anonymization techniques (plus access design and obfuscation rules) stop most exposures of the sensitive data that CWE-212 would otherwise transfer or store in the clear; the bounded remainder is data that must stay unmasked for functional reasons or where masking is not applied to every indirect identifier.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248579 OL 8 must restrict access to the kernel message buffer. blocks CWE-212, CWE-226
- V-248580 OL 8 must prevent kernel profiling by unprivileged users. blocks CWE-212
- V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. blocks CWE-212
Oracle Linux 9 (1 rule)
- V-271745 OL 9 must restrict access to the kernel message buffer. blocks CWE-212, CWE-226
RHEL 8 (1 rule)
- V-230269 RHEL 8 must restrict access to the kernel message buffer. blocks CWE-212, CWE-226
RHEL 9 (1 rule)
- V-257797 RHEL 9 must restrict access to the kernel message buffer. blocks CWE-226