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

CVE-2026-98749: tty: serial: max3100: shut down timer before freeing port

Noroxi assessment

Priority: Monitor (action score 0/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.18% (FIRST EPSS).
  • Fixed version: Linux Linux 158a07da2da720f2f98b4bea129212c6805d8ee0, 247b8f680876313586aed4d267bfcceddc2b4901, 2c8614981d3e6e000427de0ab2426ab68274d850; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 158a07da2da720f2f98b4bea129212c6805d8ee0, 247b8f680876313586aed4d267bfcceddc2b4901, 2c8614981d3e6e000427de0ab2426ab68274d850; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes 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: tty: serial: max3100: shut down timer before freeing port max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer. Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer. The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown. Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed. This issue was found by an in-house static analysis tool.

—No exploit Fix available
Published
Oct 18, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-98749

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

    • 2.6.30affected
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before d1187a7deac1e90182372a188dfe33ddd2b53cbaaffected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before cbb3fcc7cd14396ccc1379c164d96a247331f2e6affected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before fb8cefd66a6055a313c993fa9e8bed9be9b088f6affected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before 158a07da2da720f2f98b4bea129212c6805d8ee0affected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before fb668620e3b163962dabe1a674725a07aa44ff4aaffected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before 2c8614981d3e6e000427de0ab2426ab68274d850affected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before 247b8f680876313586aed4d267bfcceddc2b4901affected · git
    • 7831d56b0a3544cbb6f82f76c34ca95e24d5b676 and later · before db0949bbd06db0a75b4b1076f1e25194be7d956aaffected · git
    • before 2.6.30not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
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.10-17.2.10-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-98747Oct 18, 2026 · serial: core: fix NULL pointer dereference in serial_core_unregister_port()
    0Monitor
  • ← EarlierCVE-2026-98748Oct 18, 2026 · serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()
    0Monitor
  • Later →CVE-2026-98750Oct 18, 2026 · tty: fix saved termios reset race
    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 Linux158a07da2da720f2f98b4bea129212c6805d8ee0Vendor (CNA)
Linux Linux247b8f680876313586aed4d267bfcceddc2b4901Vendor (CNA)
Linux Linux2c8614981d3e6e000427de0ab2426ab68274d850Vendor (CNA)
Linux Linuxcbb3fcc7cd14396ccc1379c164d96a247331f2e6Vendor (CNA)
Linux Linuxd1187a7deac1e90182372a188dfe33ddd2b53cbaVendor (CNA)
Linux Linuxdb0949bbd06db0a75b4b1076f1e25194be7d956aVendor (CNA)
Linux Linuxfb668620e3b163962dabe1a674725a07aa44ff4aVendor (CNA)
Linux Linuxfb8cefd66a6055a313c993fa9e8bed9be9b088f6Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.113-1 · Debian:13Package 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 6, 2026+19 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).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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. Exploit maturity— → none
  2. 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