hwmon: (asus_atk0110) Check package count before accessing element
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2a137124664aad1e36d8d74e8e2207365a04737f, 459b0a0439ea65b2b612aa572eb62a2e26d05618, 76392d35c8df471b288cfc6536bd092b3c8ee2cf.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2a137124664aad1e36d8d74e8e2207365a04737f, 459b0a0439ea65b2b612aa572eb62a2e26d05618, 76392d35c8df471b288cfc6536bd092b3c8ee2cf or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: hwmon: (asus_atk0110) Check package count before accessing element atk_ec_present() walks the management group package returned by the GGRP ACPI method and, for each sub-package, reads its first element: id = &obj->package.elements[0]; if (id->type != ACPI_TYPE_INTEGER) without checking that the sub-package is non-empty. ACPICA allocates the element array with exactly package.count entries, so for a sub-package with a zero count this reads past the allocation. The sibling function atk_debugfs_ggrp_open() performs the same access but skips empty packages with a package.count check first. Add the same check to atk_ec_present() so a malformed firmware package cannot trigger an out-of-bounds read.
- Published
- Aug 28, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.32affected
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before 2a137124664aad1e36d8d74e8e2207365a04737faffected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before 459b0a0439ea65b2b612aa572eb62a2e26d05618affected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before 768f20e7bb48d723b82cb142120263d0806fbeb8affected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before 76392d35c8df471b288cfc6536bd092b3c8ee2cfaffected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before 981a8a2e3773dc7e704943388a1fb97970b23275affected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before d8d4fa0c4f818e30b6f6737bdd989b7e2b511caeaffected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before b770fcfcdced569bcf7c6982aeea8c3d11a21c2baffected · git
- 9e6eba610c2eb68b05841a15ece1cf929c44aea3 and later · before e2735b39f044bad7bf2017aef248935525bc0b97affected · git
- before 2.6.32not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80720Aug 28, 2026 · iomap: add a separate bio_set for iomap_split_ioend30Monitor
- ← EarlierCVE-2026-80590Aug 28, 2026 · inet: frags: strip GSO state from fragments before reassembly34Monitor
- Later →CVE-2026-80598Aug 28, 2026 · ntfs3: fix out-of-bounds read in decompress_lznt31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2a137124664aad1e36d8d74e8e2207365a04737f | Vendor (CNA) |
| Linux Linux | 459b0a0439ea65b2b612aa572eb62a2e26d05618 | Vendor (CNA) |
| Linux Linux | 76392d35c8df471b288cfc6536bd092b3c8ee2cf | Vendor (CNA) |
| Linux Linux | 768f20e7bb48d723b82cb142120263d0806fbeb8 | Vendor (CNA) |
| Linux Linux | 981a8a2e3773dc7e704943388a1fb97970b23275 | Vendor (CNA) |
| Linux Linux | b770fcfcdced569bcf7c6982aeea8c3d11a21c2b | Vendor (CNA) |
| Linux Linux | d8d4fa0c4f818e30b6f6737bdd989b7e2b511cae | Vendor (CNA) |
| Linux Linux | e2735b39f044bad7bf2017aef248935525bc0b97 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/459b0a0439ea65b2b612aa572eb62a2e26d05618
- git.kernel.org/stable/c/76392d35c8df471b288cfc6536bd092b3c8ee2cf
- git.kernel.org/stable/c/768f20e7bb48d723b82cb142120263d0806fbeb8
- git.kernel.org/stable/c/981a8a2e3773dc7e704943388a1fb97970b23275
- git.kernel.org/stable/c/b770fcfcdced569bcf7c6982aeea8c3d11a21c2b
- git.kernel.org/stable/c/d8d4fa0c4f818e30b6f6737bdd989b7e2b511cae
- git.kernel.org/stable/c/e2735b39f044bad7bf2017aef248935525bc0b97
Vendor advisories and official records. Exploit/PoC links are deliberately left out.