Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 95%

In the Linux kernel, the following vulnerability has been resolved: Revert "f2fs: remove non-uptodate folio from the page cache in move_data_block"… (CVE-2026-63813)

0
High
Published: 07/19/2026 (07/19/2026, 12:30:23 UTC)
Source: GCVE Database

Description

A race condition vulnerability in the Linux kernel's f2fs filesystem code related to page cache management has been resolved by reverting a problematic commit. The issue causes kernel panics due to list corruption when the f2fs partition is nearly full. The root cause involves a race between page cache reference dropping and folio splitting, leading to pages being freed while still linked in the LRU list, resulting in kernel crashes.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/19/2026, 20:20:02 UTC

Technical Analysis

CVE-2026-63813 addresses a race condition in the Linux kernel's f2fs filesystem, specifically in the move_data_block() function. The vulnerability arises from a commit that allowed the garbage collector path to evict the tail-end folio from the page cache, dropping page-cache references prematurely. This enables a race where split_folio_to_order() splits a folio into pages and re-adds them to the LRU list, while concurrently folio_isolate_lru() clears the PG_lru flag and takes references. If these operations race, a page can be freed while still linked in the LRU list, causing list corruption and kernel panics. The issue was resolved by reverting the commit that introduced this behavior.

Potential Impact

The vulnerability causes kernel panics and list corruption errors, leading to system instability and crashes when the f2fs partition approaches full capacity. This can disrupt system availability and may require rebooting or recovery actions.

Mitigation Recommendations

A fix is available as the vulnerability was resolved by reverting the problematic commit in the Linux kernel. Users should update to a Linux kernel version that includes this revert to prevent kernel panics related to this issue. Since this is a kernel-level fix, applying the updated kernel is the recommended remediation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-q48g-gvv8-2599
Osv Schema Version
1.4.0
Aliases
["CVE-2026-63813"]
Ecosystems
[]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a5d27ad2a4a8d59891318bf

Added to database: 07/19/2026, 19:38:21 UTC

Last enriched: 07/19/2026, 20:20:02 UTC

Last updated: 07/20/2026, 17:26:47 UTC

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses