Loading vulnerability…
CVE-2022-48637 is a use-after-free vulnerability in the Linux kernel Broadcom NetXtreme-C/E (bnxt) network driver. In the transmit-completion path, bnxt_tx_int() transfers ownership of a completed socket buffer to a Precision Time Protocol worker when transmit timestamp retrieval is required. The PTP worker can execute and free the socket buffer before bnxt_tx_int() completes its remaining processing, leaving a stale pointer that may subsequently be dereferenced or freed. The fix explicitly clears the socket-buffer pointer after ownership is handed to the worker, preventing further use in the completion path.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel Broadcom bnxt driver use-after-free involving an skb handed to a PTP worker.
Linux kernel Broadcom bnxt driver use-after-free involving socket buffers handed to a PTP worker.
Linux kernel Broadcom NetXtreme-C/E (bnxt) driver use-after-free involving socket buffers handed to a PTP worker.
A use-after-free (UAF) vulnerability in the Linux kernel Broadcom NetXtreme-C/E (bnxt) network driver, involving an skb after it is handed to a Precision Time Protocol (PTP) worker.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.