Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68362: wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin

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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 4abb4e284d8897176e91d7a3168ee29ed876bb41, 66bf998b18334ca97321433e4ab783b6ff267e9d, d6bba659ac30d862ee7bab92862cd6e514f07521; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 4abb4e284d8897176e91d7a3168ee29ed876bb41, 66bf998b18334ca97321433e4ab783b6ff267e9d, d6bba659ac30d862ee7bab92862cd6e514f07521; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.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: wifi: ath11k: fix NULL pointer dereference in ath11k_hal_srng_access_begin In ATH11K_QMI_EVENT_FW_READY, ATH11K_FLAG_REGISTERED is set unconditionally even when ath11k_core_qmi_firmware_ready() fails. This leaves the driver in an inconsistent state where initialization is considered complete although the firmware ready handling did not finish successfully. During the subsequent SSR, the driver enters the restart path based on this incorrect state and dereferences uninitialized srng members, resulting in a NULL pointer dereference. Call trace: ath11k_hal_srng_access_begin+0xc/0x60 [ath11k] (P) ath11k_ce_cleanup_pipes+0x17c/0x180 [ath11k] ath11k_core_restart+0x40/0x168 [ath11k] Fix this by: - skipping firmware_ready if ATH11K_FLAG_REGISTERED is already set - setting ATH11K_FLAG_REGISTERED only when firmware_ready succeeds - setting ATH11K_FLAG_QMI_FAIL and aborting the FW_READY handling on error Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.2.0.c2-00204-QCAMSLSWPLZ-1

—No exploit Fix available
Published
Aug 10, 2026
Updated
Aug 19, 2026
EPSS
0.1% · 6th 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-68362

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

    • 6.1affected
    • 6fe62a8cec51c756159c71be35a16b2cc8cbd4c0 and later · before 66bf998b18334ca97321433e4ab783b6ff267e9daffected · git
    • 6fe62a8cec51c756159c71be35a16b2cc8cbd4c0 and later · before e517e207300edcf7f3a8f6c45f9155c0e419ffb9affected · git
    • 6fe62a8cec51c756159c71be35a16b2cc8cbd4c0 and later · before d6bba659ac30d862ee7bab92862cd6e514f07521affected · git
    • 6fe62a8cec51c756159c71be35a16b2cc8cbd4c0 and later · before e5394605f9a985cc3a8263e610ba84b33cbe7b0caffected · git
    • 6fe62a8cec51c756159c71be35a16b2cc8cbd4c0 and later · before 4abb4e284d8897176e91d7a3168ee29ed876bb41affected · git
    • 6fe62a8cec51c756159c71be35a16b2cc8cbd4c0 and later · before e8d85672dd7e2523f774caafba8f858384e18df7affected · git
    • before 6.1not affected · semver
    • 6.1.183 and later · up to and including 6.1.*not affected · semver
    • 6.6.148 and later · up to and including 6.6.*not 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.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.6-17.1.6-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-68360Aug 10, 2026 · hwmon: (corsair-cpro) Stop device IO before calling hid_hw_stop
    0Monitor
  • ← EarlierCVE-2026-68361Aug 10, 2026 · hwmon: (corsair-psu) Stop device IO before calling hid_hw_stop
    0Monitor
  • Later →CVE-2026-68363Aug 10, 2026 · wifi: ath9k: hif_usb: don't dereference hif_dev after re-arming firmware request
    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 Linux4abb4e284d8897176e91d7a3168ee29ed876bb41Vendor (CNA)
Linux Linux66bf998b18334ca97321433e4ab783b6ff267e9dVendor (CNA)
Linux Linuxd6bba659ac30d862ee7bab92862cd6e514f07521Vendor (CNA)
Linux Linuxe517e207300edcf7f3a8f6c45f9155c0e419ffb9Vendor (CNA)
Linux Linuxe5394605f9a985cc3a8263e610ba84b33cbe7b0cVendor (CNA)
Linux Linuxe8d85672dd7e2523f774caafba8f858384e18df7Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-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.

No dated events beyond publication.

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

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. Fix✗ → ✓

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

References

Show all references (5 more)

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

All records