🛡️ USN-7591-5 — linux-intel-iotg
Description
linux-intel-iotg vulnerabilities
Michael Randrianantenaina discovered that the Bluetooth driver in the Linux
Kernel contained an improper access control vulnerability. A nearby
attacker could use this to connect a rougue device and possibly execute
arbitrary code. (CVE-2024-8805)
It was discovered that the CIFS network file system implementation in the
Linux kernel did not properly verify the target namespace when handling
upcalls. An attacker could use this to expose sensitive information.
(CVE-2025-2312)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- PowerPC architecture;
- x86 architecture;
- ACPI drivers;
- Clock framework and drivers;
- GPU drivers;
- HID subsystem;
- InfiniBand drivers;
- Media drivers;
- MemoryStick subsystem;
- Network drivers;
- Mellanox network drivers;
- NTB driver;
- PCI subsystem;
- Voltage and Current Regulator drivers;
- Remote Processor subsystem;
- SCSI subsystem;
- QCOM SoC drivers;
- Thermal drivers;
- BTRFS file system;
- Ext4 file system;
- JFS file system;
- Network file system (NFS) server daemon;
- NTFS3 file system;
- File systems infrastructure;
- Proc file system;
- SMB network file system;
- IPv6 networking;
- RDMA verbs API;
- SoC audio core drivers;
- Tracing infrastructure;
- Watch queue notification mechanism;
- 802.1Q VLAN protocol;
- Asynchronous Transfer Mode (ATM) subsystem;
- Bluetooth subsystem;
- Networking core;
- IPv4 networking;
- Netfilter;
- Network traffic control;
- SMC sockets;
- SoC Audio for Freescale CPUs drivers;
(CVE-2025-23138, CVE-2025-21956, CVE-2025-21970, CVE-2025-22025,
CVE-2024-46753, CVE-2025-21962, CVE-2025-37889, CVE-2025-21992,
CVE-2025-39728, CVE-2025-22054, CVE-2025-21959, CVE-2024-53144,
CVE-2022-49728, CVE-2024-58093, CVE-2025-38637, CVE-2025-21981,
CVE-2025-21963, CVE-2025-21968, CVE-2025-22014, CVE-2024-46812,
CVE-2025-22005, CVE-2025-21994, CVE-2025-22071, CVE-2025-22008,
CVE-2022-49636, CVE-2025-22007, CVE-2023-53034, CVE-2025-22035,
CVE-2025-22010, CVE-2025-22081, CVE-2025-22021, CVE-2024-46821,
CVE-2025-21999, CVE-2025-38575, CVE-2025-22073, CVE-2025-22004,
CVE-2024-42230, CVE-2025-21941, CVE-2024-56664, CVE-2025-22044,
CVE-2025-39735, CVE-2025-22060, CVE-2025-22055, CVE-2025-21957,
CVE-2025-21975, CVE-2025-22075, CVE-2025-22089, CVE-2025-37937,
CVE-2025-38152, CVE-2025-22020, CVE-2025-22066, CVE-2025-22056,
CVE-2025-22050, CVE-2025-21964, CVE-2025-21996, CVE-2025-22079,
CVE-2025-23136, CVE-2025-22063, CVE-2024-36945, CVE-2025-22097,
CVE-2025-37785, CVE-2025-21991, CVE-2025-22086, CVE-2025-22045,
CVE-2025-22018)
Affected software
USN-7591-5 is recorded against 1 package.
- linux-intel-iotg (fixed in 5.15.0-1081.87)
Timeline and source
Published on 4 July 2025 and last revised on 6 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Advisory)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
ubuntu.com (Report)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux-intel-iotg | — | 5.15.0-1081.87 |
References
Similar Threats
- Unknown UBUNTU-CVE-2021-4454
- Unknown UBUNTU-CVE-2021-47631
- Unknown UBUNTU-CVE-2021-47632
- Unknown UBUNTU-CVE-2021-47633
- Unknown UBUNTU-CVE-2021-47634
More USN 7 advisories
Browse all of USN 7 in the advisory index.
Free Vulnerability Check
Is your site affected by USN-7591-5?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against USN-7591-5 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.