Security readout for executives and security teams
Plain-English summary
A flaw in the Linux nct6775 hardware-monitoring driver can make the kernel access data outside the expected temperature-configuration register array. It was detected by Kernel Address Sanitizer during driver initialization. The supplied CVSS score is 7.3, but the evidence does not establish real-world exploitation or confirm practical impact beyond the reported out-of-bounds access.
Executive priority
Schedule an expedited, targeted kernel update for systems using nct6775, especially shared systems permitting untrusted local access. The high CVSS score warrants attention, but the evidence does not support an organization-wide emergency response based on remote or active exploitation.
Technical view
The nct6775 probe logic can encounter more temperature registers than temperature-configuration registers. That count mismatch causes a global out-of-bounds access in nct6775_probe, reported when KASAN is enabled. The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction, with potentially high confidentiality and availability impact.
Likely exposure
Exposure is limited to Linux systems whose kernels contain the affected nct6775 hwmon code and probe compatible hardware. The bundle identifies entries associated with versions 6.6, 6.6.19, 6.7.7, and 6.8, but does not provide reliable range semantics. Confirm exposure through the applicable Linux distributor or kernel stable-branch guidance.
Exploitation context
The CVE is not listed as KEV, and no supplied source reports active exploitation or a public exploit. The CVSS vector indicates that exploitation would require local, low-privileged access. Whether the KASAN finding is practically exploitable for the scored confidentiality, integrity, or availability impacts is not established by the bundle.
Researcher notes
The root condition is a mismatch between temperature-register and temperature-configuration-register counts during probing. Four stable-kernel fix commits are referenced, but the bundle does not map each commit to precise affected or fixed release ranges. No CWE is supplied. Validate branch-specific backports and avoid treating KASAN detection alone as proof of weaponizable impact.
Mitigation direction
- Identify systems using the nct6775 hardware-monitoring driver and map their kernels against vendor advisories.
- Apply a vendor-supported kernel update incorporating the appropriate referenced stable fix.
- Prioritize multi-user or otherwise untrusted local-access systems because the CVSS vector requires low privileges.
- If updates are delayed, consult vendor guidance for safe mitigations; none are specified in the bundle.
Validation and detection
- Confirm the running kernel build and whether nct6775 is present, loaded, or probed on the hardware.
- Verify the installed kernel contains the matching stable fix or a distributor-documented backport.
- Review kernel and KASAN logs for nct6775 probe-time out-of-bounds reports or related access errors.
- Retest hardware-monitoring initialization after updating and confirm temperatures remain available without access errors.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2024-26730 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H1.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/745aa03c513f1ba12cb98495467676f7acf3fffdCVE reference, Linux
- https://git.kernel.org/stable/c/f006c45a3ea424f8f6c8e4b9283bc245ce2a4d0fCVE reference, Linux
- https://git.kernel.org/stable/c/c196387820c9214c5ceaff56d77303c82514b8b1CVE reference, Linux
- https://git.kernel.org/stable/c/d56e460e19ea8382f813eb489730248ec8d7eb73CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.