Vulnerabilities

Vulnerability · USN-8575-1

linux, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-hwe-5.15, linux-kvm, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-realtime, linux-xilinx-zynqmp vulnerabilitie

Published Jul 21, 2026 · catalog updated Oct 23, 2026 · linux, linux-gcp, linux-gcp-fips, linux-gke,

Open the advisory

Exploitation likelihood is not on this record for USN-8575-1. A missing EPSS score is not a low risk. Compare linux, linux-gcp, linux-gcp-fips, linux-gke, with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (linux, linux-gcp, linux-gcp-fips, linux-gke,).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
Ubuntu:22.04:LTS linux · Ubuntu:22.04:LTS linux-gcp · Ubuntu:22.04:LTS linux-gke · Ubuntu:22.04:LTS linux-gkeop · Ubuntu:22.04:LTS linux-kvm · Ubuntu:22.04:LTS linux-lowlatency

Maxim Suhanov discovered that the NTFS file system implementation in the Linux kernel did not properly validate file name length in certain situations, leading to an out-of-bounds read. An attacker could use this to construct a malicious NTFS image that, when mounted and operated on, could expose sensitive information (kernel memory). (CVE-2023-45896) It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. (CVE-2025-54505) It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) 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: - ARM32 architecture; - ARM64 architecture; - MIPS architecture; - PowerPC architecture; - S390 architecture; - x86 architecture; - Block layer subsystem; - Cryptographic API; - ACPI drivers; - ATM drivers; - Drivers core; - Power management core; - DRBD Distributed Replicated Block Device drivers; - RNBD block device driver; - Bluetooth drivers; - Bus devices; - Character device driver; - TPM device driver; - Clocksource drivers; - Data acquisition framework and drivers; - CPU frequency scaling framework; - CPU idle management framework; - Hardware crypto device drivers; - DMA engine subsystem; - Arm Firmware Framework for ARMv8-A(FFA); - EFI core; - GPIO subsystem; - GPU drivers; - HID subsystem; - Hardware monitoring drivers; - I2C subsystem; - IIO subsystem; - IIO ADC drivers; - InfiniBand drivers; - Input Device (Miscellaneous) drivers; - IOMMU subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - MediaTek SMI driver; - NVIDIA Te

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Ubuntu:22.04:LTS linux0 → 5.15.0-186.196
  • Ubuntu:22.04:LTS linux-gcp0 → 5.15.0-1112.122
  • Ubuntu:22.04:LTS linux-gke0 → 5.15.0-1108.114
  • Ubuntu:22.04:LTS linux-gkeop0 → 5.15.0-1095.103
  • Ubuntu:22.04:LTS linux-kvm0 → 5.15.0-1104.109
  • Ubuntu:22.04:LTS linux-lowlatency0 → 5.15.0-184.194
  • Ubuntu:22.04:LTS linux-xilinx-zynqmp0 → 5.15.0-1075.79
  • Ubuntu:Pro:20.04:LTS linux-hwe-5.150 → 5.15.0-186.196~20.04.1
  • Ubuntu:Pro:20.04:LTS linux-lowlatency-hwe-5.150 → 5.15.0-184.194~20.04.1
  • Ubuntu:Pro:FIPS-updates:22.04:LTS linux-gcp-fips0 → 5.15.0-1112.122+fips1
  • Ubuntu:Pro:Realtime:22.04:LTS linux-realtime0 → 5.15.0-1111.120

How to fix USN-8575-1

  • Recommended remediation

    A patch or advisory reference is linked. Open the original publisher for availability by product version.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for USN-8575-1. A missing EPSS score is not a low risk. Compare linux, linux-gcp, linux-gcp-fips, linux-gke, with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 5.15.0-186.196, 0 → 5.15.0-1112.122, 0 → 5.15.0-1108.114, 0 → 5.15.0-1095.103, 0 → 5.15.0-1104.109, 0 → 5.15.0-184.194. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jul 21, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    Maxim Suhanov discovered that the NTFS file system implementation in the Linux kernel did not properly validate file name length in certain situations, leading to an out-of-bounds read. An attacker could use this to construct a malicious NTFS image that, when mounted and operated on, could expose sensitive information (kernel memory). (CVE-2023-45896) It was discovered that some AMD processors did

  2. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-hwe-5.15 fixed in 5.15.0-186.196~20.04.1; linux-lowlatency-hwe-5.15 fixed in 5.15.0-184.194~20.04.1; linux fixed in 5.15.0-186.196; linux-gcp fixed in 5.15.0-1112.122

  3. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-hwe-5.15 fixed in 5.15.0-186.196~20.04.1

  4. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-lowlatency-hwe-5.15 fixed in 5.15.0-184.194~20.04.1

  5. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux fixed in 5.15.0-186.196

  6. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-gcp fixed in 5.15.0-1112.122

  7. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-gke fixed in 5.15.0-1108.114

  8. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-gkeop fixed in 5.15.0-1095.103

  9. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-kvm fixed in 5.15.0-1104.109

  10. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-lowlatency fixed in 5.15.0-184.194

  11. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-xilinx-zynqmp fixed in 5.15.0-1075.79

  12. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-realtime fixed in 5.15.0-1111.120

  13. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    linux-gcp-fips fixed in 5.15.0-1112.122+fips1

  14. Oct 23, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    Maxim Suhanov discovered that the NTFS file system implementation in the Linux kernel did not properly validate file name length in certain situations, leading to an out-of-bounds read. An attacker could use this to construct a malicious NTFS image that, when mounted and operated on, could expose sensitive information (kernel memory). (CVE-2023-45896) It was discovered that some AMD processors did

Sources

  • OpenSSF OSV / OSV ScannerPackage advisoryUSN-8575-1

    linux, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-hwe-5.15, linux-kvm, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-realtime, linux-xilinx-zynqmp vulnerabilities

    osv.dev

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.