Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54053: wifi: iwlwifi: pcie: fix possible NULL pointer dereference

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.25% (FIRST EPSS).
  • Fixed version: Linux Linux 0f9a1bcb94016d3a3c455a77b01f6bb06e15f6eb, 0fc0d287c1e7dcb39a3b9bb0f8679cd68c2156c7, 7545f21eee1356ec98581125c4dba9c4c0cc7397.

Low priority for now. Upgrade to Linux Linux 0f9a1bcb94016d3a3c455a77b01f6bb06e15f6eb, 0fc0d287c1e7dcb39a3b9bb0f8679cd68c2156c7, 7545f21eee1356ec98581125c4dba9c4c0cc7397 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: iwlwifi: pcie: fix possible NULL pointer dereference It is possible that iwl_pci_probe() will fail and free the trans, then afterwards iwl_pci_remove() will be called and crash by trying to access trans which is already freed, fix it. iwlwifi 0000:01:00.0: Detected crf-id 0xa5a5a5a2, cnv-id 0xa5a5a5a2 wfpm id 0xa5a5a5a2 iwlwifi 0000:01:00.0: Can't find a correct rfid for crf id 0x5a2 ... BUG: kernel NULL pointer dereference, address: 0000000000000028 ... RIP: 0010:iwl_pci_remove+0x12/0x30 [iwlwifi] pci_device_remove+0x3e/0xb0 device_release_driver_internal+0x103/0x1f0 driver_detach+0x4c/0x90 bus_remove_driver+0x5c/0xd0 driver_unregister+0x31/0x50 pci_unregister_driver+0x40/0x90 iwl_pci_unregister_driver+0x15/0x20 [iwlwifi] __exit_compat+0x9/0x98 [iwlwifi] __x64_sys_delete_module+0x147/0x260

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 16th 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.2%

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-2023-54053

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

    • 5.4affected
    • 809805a820c6445f7a701ded24fdc6bbc841d1e4 and later · before f6f2d16c77f936041b8ac495fceabded4ec6c83caffected · git
    • 809805a820c6445f7a701ded24fdc6bbc841d1e4 and later · before 0fc0d287c1e7dcb39a3b9bb0f8679cd68c2156c7affected · git
    • 809805a820c6445f7a701ded24fdc6bbc841d1e4 and later · before 7545f21eee1356ec98581125c4dba9c4c0cc7397affected · git
    • 809805a820c6445f7a701ded24fdc6bbc841d1e4 and later · before 0f9a1bcb94016d3a3c455a77b01f6bb06e15f6ebaffected · git
    • 809805a820c6445f7a701ded24fdc6bbc841d1e4 and later · before dcd23aa6cc0ded7950b60ce1badb80b84045c6c0affected · git
    • 809805a820c6445f7a701ded24fdc6bbc841d1e4 and later · before b655b9a9f8467684cfa8906713d33b71ea8c8f54affected · git
    • before 5.4not affected · semver
    • 5.4.244 and later · up to and including 5.4.*not affected · semver
    • 5.10.181 and later · up to and including 5.10.*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.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-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-2023-54051Dec 24, 2025 · net: do not allow gso_size to be set to GSO_BY_FRAGS
    0Monitor
  • ← EarlierCVE-2023-54052Dec 24, 2025 · wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU
    0Monitor
  • Later →CVE-2023-54055Dec 24, 2025 · RDMA/irdma: Fix memory leak of PBLE objects
    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 Linux0f9a1bcb94016d3a3c455a77b01f6bb06e15f6ebVendor (CNA)
Linux Linux0fc0d287c1e7dcb39a3b9bb0f8679cd68c2156c7Vendor (CNA)
Linux Linux7545f21eee1356ec98581125c4dba9c4c0cc7397Vendor (CNA)
Linux Linuxb655b9a9f8467684cfa8906713d33b71ea8c8f54Vendor (CNA)
Linux Linuxdcd23aa6cc0ded7950b60ce1badb80b84045c6c0Vendor (CNA)
Linux Linuxf6f2d16c77f936041b8ac495fceabded4ec6c83cVendor (CNA)
debian:linux6.1.37-1 · 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.

No history yet (it accumulates with the daily EPSS job).

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