Linux Kernel up to 6.19.8 xfs privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.7$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 6.19.8. Affected by this issue is some unknown functionality of the component xfs. This manipulation causes an unknown weakness. This vulnerability is registered as CVE-2026-43365. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.8. It has been declared as critical. Affected by this vulnerability is an unknown code of the component xfs. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: xfs: fix undersized l_iclog_roundoff values If the superblock doesn't list a log stripe unit, we set the incore log roundoff value to 512. This leads to corrupt logs and unmountable filesystems in generic/617 on a disk with 4k physical sectors... XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Torn write (CRC failure) detected at log block 0x318e. Truncating head block from 0x3197. XFS (sda1): failed to locate log tail XFS (sda1): log mount/recovery failed: error -74 XFS (sda1): log mount failed XFS (sda1): Mounting V5 Filesystem ff3121ca-26e6-4b77-b742-aaff9a449e1c XFS (sda1): Ending clean mount ...on the current xfsprogs for-next which has a broken mkfs. xfs_info shows this... meta-data=/dev/sda1 isize=512 agcount=4, agsize=644992 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=1 = reflink=1 bigtime=1 inobtcount=1 nrext64=1 = exchange=1 metadir=1 data = bsize=4096 blocks=2579968, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1, parent=1 log =internal log bsize=4096 blocks=16384, version=2 = sectsz=4096 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 = rgcount=0 rgsize=268435456 extents = zoned=0 start=0 reserved=0 ...observe that the log section has sectsz=4096 sunit=0, which means that the roundoff factor is 512, not 4096 as you'd expect. We should fix mkfs not to generate broken filesystems, but anyone can fuzz the ondisk superblock so we should be more cautious. I think the inadequate logic predates commit a6a65fef5ef8d0, but that's clearly going to require a different backport.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-43365 since 05/01/2026. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/27/2026).

The vulnerability scanner Nessus provides a plugin with the ID 313444 (Linux Distros Unpatched Vulnerability : CVE-2026-43365), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.15.203, 6.1.167, 6.6.130, 6.12.78, 6.18.19 or 6.19.9 eliminates this vulnerability. Applying the patch 5afae524f83d6a18517298491a5624cb0eae5029/2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40/41e91dff2d3974730b5ee50daa8e27ec254cbf91/e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d/446a1f5bb64ba38adb93cb043ff0f7b85e8937ca/5e7148402dfc4a5b7894d8e97b15e5c2e70924aa/52a8a1ba883defbfe3200baa22cf4cd21985d51a is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (313444) and CERT Bund (WID-SEC-2026-1454). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Red Hat OpenShift
  • Microsoft Azure Linux
  • Open Source Linux Kernel
  • Proxmox Virtual Environment

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.8
VulDB Meta Temp Score: 6.7

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 8.2
CNA Vector (Linux): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 313444
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-43365

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.203/6.1.167/6.6.130/6.12.78/6.18.19/6.19.9
Patch: 5afae524f83d6a18517298491a5624cb0eae5029/2ecda4b83749c1fef0c9dea4fd5e8b513aba3e40/41e91dff2d3974730b5ee50daa8e27ec254cbf91/e88ce9f0536f3b2149afb70625cfc4bd74a4ac6d/446a1f5bb64ba38adb93cb043ff0f7b85e8937ca/5e7148402dfc4a5b7894d8e97b15e5c2e70924aa/52a8a1ba883defbfe3200baa22cf4cd21985d51a

Timelineinfo

05/01/2026 CVE reserved
05/08/2026 +7 days Advisory disclosed
05/08/2026 +0 days VulDB entry created
07/27/2026 +80 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-43365 (🔒)
GCVE (CVE): GCVE-0-2026-43365
GCVE (VulDB): GCVE-100-362275
CERT Bund: WID-SEC-2026-1454 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 05/08/2026 18:40
Updated: 07/27/2026 06:40
Changes: 05/08/2026 18:40 (57), 05/09/2026 12:44 (2), 05/18/2026 09:55 (11), 06/19/2026 07:27 (7), 07/27/2026 06:40 (3)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!