CVE-2026-68084

staging: vme_user: fix location monitor leak in tsi148 bridge

N/A

Published: August 10, 2026 at 11:51 AM UTC

Updated: August 17, 2026 at 05:18 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: staging: vme_user: fix location monitor leak in tsi148 bridge tsi148_probe() allocates a location monitor resource and links it into tsi148_bridge->lm_resources. The probe error path frees this list, but tsi148_remove() only frees the dma, slave and master resource lists, so the location monitor resource is leaked on device unbind or module unload. Free the lm_resources list in tsi148_remove() as well, before tsi148_bridge is freed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

2.6.32 ≤ v < 6.1.1782.6.32 ≤ v < 6.12.962.6.32 ≤ v < 6.18.392.6.32 ≤ v < 6.6.1452.6.32 ≤ v < 7.1.42.6.32 ≤ v < 7.22.6.32d22b8ed9a3b0a157b732580258ec16b729265953

Vendor states this is fixed in 151edde741f8bc7f2931c5f44ab376d32b0c8beb (fixed)

Vendor states this is fixed in 18be0ad31b161a8b6fbc90d14355ad40c061b6b0 (fixed)

Vendor states this is fixed in 36902ab588ccc2fa07994adf6c5f51cbfe379177 (fixed)

Vendor states this is fixed in c6cda17e98545980e42291fc4282daa8a8ebe384 (fixed)

Vendor states this is fixed in e3ceafa6d8ee6b3a0f7fabe7a551fda909edbd46 (fixed)

Vendor states this is fixed in eef048dd77ebfbf99d7c28f9e9dd331d2af7b6f6 (fixed)

Vendor states this is fixed in 2.6.32 (unaffected)

Vendor states this is fixed in 6.1.178 (unaffected)

Vendor states this is fixed in 6.12.96 (unaffected)

Vendor states this is fixed in 6.18.39 (unaffected)

Vendor states this is fixed in 6.6.145 (unaffected)

Vendor states this is fixed in 7.1.4 (unaffected)