CVE-2023-53034 is an incorrect bitwise-shift vulnerability in the Linux kernel Switchtec non-transparent bridge driver. The switchtec_ntb_mw_set_trans function can be reached through ntb_mw_clear_trans, which supplies zero values for both the address and size parameters. This input causes the calculated xlate_pos value to become negative before it is used as the shift count in a BIT operation, producing an invalid negative shift exponent. The fix validates that xlate_pos is non-negative before performing the bit operation.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in ntb_hw_switchtec involving a shift-out-of-bounds condition in switchtec_ntb_mw_set_trans.
A Linux kernel vulnerability in ntb_hw_switchtec involving a shift-out-of-bounds condition in switchtec_ntb_mw_set_trans.
A Linux kernel shift-out-of-bounds vulnerability in ntb_hw_switchtec/switchtec_ntb_mw_set_trans.
A Linux kernel vulnerability in ntb_hw_switchtec involving a shift-out-of-bounds issue in switchtec_ntb_mw_set_trans.
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.