Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98499: HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce()

Noroxi assessment

Priority: Monitor (action score 32/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.39% (FIRST EPSS).
  • Someone on the same network segment 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 26471d954bbfbfb9032994f7f485802ee20e0582, 456afe4707e23cc114ad833197f63b52bb8fd1e7, 4b09b7c84b8633cd041181616bd15bf5e73c164d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 26471d954bbfbfb9032994f7f485802ee20e0582, 456afe4707e23cc114ad833197f63b52bb8fd1e7, 4b09b7c84b8633cd041181616bd15bf5e73c164d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 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: HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce() The 'wacom_wac_pen_serial_enforce()' function may calculate and pass an invalid offset to hid_field_extract(), resulting in memory reads at incorrect addresses -- possibly beyond the end of the report. If a field in the HID descriptor lists more usages than its Report Count actually reserves space for, the function's inner 'j' will walk past the end of the field: for (i = 0; i < report->maxfield; i++) { for (j = 0; j < report->field[i]->maxusage; j++) { ... value = hid_field_extract(hdev, raw_data + 1, offset + j * size, size); A descriptor listing 12288 usages against Report Count 1 has the loop extract the usage at index 12287 from bit offset 98296 -- about 12 KB past a 2-byte received report. The value is stored in wacom_wac->serial[0] and can reach userspace as an MSC_SERIAL event, making this an information disclosure. Clamp the loop to field->report_count, the number of value slots the report holds. Value slots past the last declared usage are still scanned; they reuse that usage (HID 1.11, 6.2.2.8). Verified on v6.12.105 with a UHID reproducer: a 2-byte report from such a descriptor trips KASAN before the patch and not after it.

HighCVSS 8.1 · v3.1—No exploit Fix available
Published
Oct 18, 2026
Updated
Oct 24, 2026
EPSS
0.3% · 33th percentile
CWE
—

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CNA vs NVD score

NVD
—
CNA · Linux
8.1
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.

Follow CVE-2026-98499

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 4.16affected
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before 9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51affected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before 26471d954bbfbfb9032994f7f485802ee20e0582affected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before 456afe4707e23cc114ad833197f63b52bb8fd1e7affected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before 65e7c4b5366b770c60dfefac3f1d06e33a9e411eaffected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before eaa7d29341ef4b91e84ad097562982288a7c376caffected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before c3129e6f26e18c0886ede7265f187a7ec289e1d1affected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before 4b09b7c84b8633cd041181616bd15bf5e73c164daffected · git
    • 83417206427bdf0fef9fa69957807194f25923c3 and later · before 9aa237cf66495b2426ddde8532e9b08a0ed83aaaaffected · git
    • before 4.16not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.9-17.2.9-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98497Oct 18, 2026 · net/mlx5e: fix swapped IPv6 IPsec policy masks
    30Monitor
  • ← EarlierCVE-2026-98498Oct 18, 2026 · net/mlx5: Fix rev_entry reference leak in mlx5_tc_ct_shared_counter_get()
    0Monitor
  • Later →CVE-2026-98500Oct 18, 2026 · HID: hid-oxp: use cancel_delayed_work_sync() in remove
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux26471d954bbfbfb9032994f7f485802ee20e0582Vendor (CNA)
Linux Linux456afe4707e23cc114ad833197f63b52bb8fd1e7Vendor (CNA)
Linux Linux4b09b7c84b8633cd041181616bd15bf5e73c164dVendor (CNA)
Linux Linux65e7c4b5366b770c60dfefac3f1d06e33a9e411eVendor (CNA)
Linux Linux9aa237cf66495b2426ddde8532e9b08a0ed83aaaVendor (CNA)
Linux Linux9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51Vendor (CNA)
Linux Linuxc3129e6f26e18c0886ede7265f187a7ec289e1d1Vendor (CNA)
Linux Linuxeaa7d29341ef4b91e84ad097562982288a7c376cVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.159.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package 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.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 5, 2026+18 d
EPSS, last 120 days

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 researchers

Finders, 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.

All national notices →

Technical details

Attack conditions

  • Someone on the same network segment 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
none
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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

  1. CVSS— → 8.1
  2. Severity— → high
  3. Exploit maturity— → none
  4. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records