Linux Kernel up to 6.17.3 ext4 kvmalloc allocation of resources

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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.15.194/6.1.156/6.6.112/6.12.53/6.17.3. Impacted is the function kvmalloc of the component ext4. The manipulation leads to allocation of resources. This vulnerability is traded as CVE-2025-40179. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.15.194/6.1.156/6.6.112/6.12.53/6.17.3 and classified as critical. This issue affects the function kvmalloc of the component ext4. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: ext4: verify orphan file size is not too big In principle orphan file can be arbitrarily large. However orphan replay needs to traverse it all and we also pin all its buffers in memory. Thus filesystems with absurdly large orphan files can lead to big amounts of memory consumed. Limit orphan file size to a sane value and also use kvmalloc() for allocating array of block descriptor structures to avoid large order allocations for sane but large orphan files.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-40179 since 04/16/2025. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 276782 (Debian dla-4379 : linux-config-6.1 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.15.195, 6.1.157, 6.6.113, 6.12.54, 6.17.4 or 6.18-rc1 eliminates this vulnerability. Applying the patch 95a21611b14ae0a401720645245a8db16f040995/566a1d6084563bd07433025aa23bcea4427de107/304fc34ff6fc8261138fd81f119e024ac3a129e9/a2d803fab8a6c6a874277cb80156dc114db91921/2b9da798ff0f4d026c5f0f815047393ebe7d8859/0a6ce20c156442a4ce2a404747bb0fb05d54eeb3 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 (276782) and CERT Bund (WID-SEC-2025-2595). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

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

CVSSv2info

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

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

Exploitinginfo

Class: Allocation of resources
CWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 276782
Nessus Name: Debian dla-4379 : linux-config-6.1 - security update

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.195/6.1.157/6.6.113/6.12.54/6.17.4/6.18-rc1
Patch: 95a21611b14ae0a401720645245a8db16f040995/566a1d6084563bd07433025aa23bcea4427de107/304fc34ff6fc8261138fd81f119e024ac3a129e9/a2d803fab8a6c6a874277cb80156dc114db91921/2b9da798ff0f4d026c5f0f815047393ebe7d8859/0a6ce20c156442a4ce2a404747bb0fb05d54eeb3

Timelineinfo

04/16/2025 CVE reserved
11/13/2025 +211 days Advisory disclosed
11/13/2025 +0 days VulDB entry created
02/05/2026 +84 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-40179 (🔒)
GCVE (CVE): GCVE-0-2025-40179
GCVE (VulDB): GCVE-100-332249
CERT Bund: WID-SEC-2025-2595 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 11/13/2025 07:28
Updated: 02/05/2026 11:12
Changes: 11/13/2025 07:28 (59), 11/13/2025 17:08 (7), 11/28/2025 23:34 (2), 12/01/2025 14:10 (1), 12/21/2025 20:23 (1), 02/05/2026 11:12 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!