cve.bz

CVE-2026-63811 linux linux kernel: NULL Pointer Dereference

5.5 mediumEPSS 0.09%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.09% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: f2fs: read COW data with the original inode during atomic write When updating an atomic-write file, f2fs_write_begin() may read the previously written data back from the COW inode: prepare_atomic_write_begin() locates the block in the COW inode and sets use_cow, and the read bio is then built with the COW inode: f2fs_submit_page_read(use_cow ? F2FS_I(inode)->cow_inode : inode, ...); and f2fs_grab_read_bio() decides whether to schedule fs-layer decryption (STEP_DECRYPT) for the bio based on that inode via fscrypt_inode_uses_fs_layer_crypto(). However, the folio being filled belongs to the original inode (folio->mapping->host == inode), and the data stored in the COW block was encrypted (or left as plaintext) using the original inode's context, not the COW inode's -- see f2fs_encrypt_one_page(), which keys off fio->page->mapping->host. fscrypt_decrypt_pagecache_blocks() likewise operates on folio->mapping->host. The COW inode is created as a tmpfile in the parent directory and inherits its encryption policy from there. With test_dummy_encryption the newly created COW inode gets the dummy policy and becomes encrypted, while a pre-existing regular file -- created before the policy applied, e.g. already present in the on-disk image -- stays unencrypted. The read path then sets STEP_DECRYPT based on the encrypted COW inode and calls fscrypt_decrypt_pagecache_blocks() on a folio whose host (the unencrypted original inode) has a NULL ->i_crypt_info, dereferencing it: Oops: general protection fault, probably for non-canonical address ... KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] RIP: 0010:fscrypt_decrypt_pagecache_blocks+0xa0/0x310 Workqueue: f2fs_post_read_wq f2fs_post_read_work Call Trace: fscrypt_decrypt_bio+0x1eb/0x340 f2fs_post_read_work+0xba/0x140 process_one_work+0x91c/0x1a40 worker_thread+0x677/0xe90 kthread+0x2bc/0x3a0 The COW inode is only needed to locate the on-disk block, and that block address is already resolved into @blkaddr by prepare_atomic_write_begin() via __find_data_block(cow_inode, ...); f2fs_submit_page_read() then reads from that physical @blkaddr directly, so the inode argument only selects the post-read crypto context, not which block is fetched. Reading with @inode therefore returns the same (latest, not-yet-committed) COW data, while making both the fs-layer decryption decision and the inline crypto path use the correct (original inode's) key. With the COW inode no longer used at the read site, the use_cow flag has no remaining consumer; drop it from f2fs_write_begin() and prepare_atomic_write_begin().

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.09% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-63811 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63811?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63811?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63811 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.4 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.57
Linux7.17.1.3
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-63811
Debian13linux6.12.115-2DEBIAN-CVE-2026-63811
Debian14linux7.1.3-1DEBIAN-CVE-2026-63811
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-63811
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-63811
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-63811
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-63811
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 42 moreno fix listedUBUNTU-CVE-2026-63811
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1012.12~24.04.1UBUNTU-CVE-2026-63811 USN-8726-1
Ubuntu24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-63811 USN-8728-2
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-63811
Ubuntu24.04:LTSlinux-gcp-7.0, linux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-63811 USN-8728-1 USN-8728-3
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-31.31~24.04.1UBUNTU-CVE-2026-63811 USN-8726-1
Ubuntu24.04:LTSlinux-nvidia-7.07.0.0-1018.18~24.04.1UBUNTU-CVE-2026-63811 USN-8760-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-31.31.1~24.04.1UBUNTU-CVE-2026-63811
14 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.1.4-1.1openSUSE-SU-2026:11339-1
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-63811
Alpaquitastreamlinux-lts6.18.58-r0BELL-CVE-2026-63811

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-63811.

History

  1. Scored 5.5 medium
  2. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON