In the Linux kernel, the following vulnerability has been resolved:
wifi: rtlwifi: remove unused check_buddy_priv
Commit 2461c7d60f9f ("rtlwifi: Update header file") introduced a global
list of private data structures.
Later on, commit 26634c4b1868 ("rtlwifi Modify existing bits to match
vendor version 2013.02.07") started adding the private data to that list at
probe time and added a hook, check_buddy_priv to find the private data from
a similar device.
However, that function was never used.
Besides, though there is a lock for that list, it is never used. And when
the probe fails, the private data is never removed from the list. This
would cause a second probe to access freed memory.
Remove the unused hook, structures and members, which will prevent the
potential race condition on the list and its corruption during a second
probe when probe fails.
CVSS
7.8 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
from 26634c4b1868323f49f8cd24c3493b57819867fd before f801e754efa21bd61b3cc15ec7565696165b272f; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 1b9cbd8a9ae68b32099fbb03b2d5ffa0c5e0dcc9; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 8e2fcc68fbaab3ad9f5671fee2be0956134b740a; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 1e39b0486cdb496cdfba3bc89886150e46acf6f4; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 465d01ef6962b82b1f0ad1f3e58b398dbd35c1c1; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 543e3e9f2e9e47ded774c74e680f28a0ca362aee; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 006e803af7408c3fc815b0654fc5ab43d34f0154; 26634c4b1868323f49f8cd24c3493b57819867fd builds before 2fdac64c3c35858aa8ac5caa70b232e03456e120
from 3.10 before 5.4.291; from 5.5 before 5.10.235; from 5.11 before 5.15.179; from 5.16 before 6.1.129; from 6.2 before 6.6.76; from 6.7 before 6.12.13; from 6.13 before 6.13.2
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.