data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-43463 in the interactive tracker

CVE-2026-43463

rxrpc, afs: Fix missing error pointer check after rxrpc_kernel_lookup_peer()

EPSS 0.2%

Published 2026-05-08 (5 months ago) by the Linux kernel CNA. Subsystem fs/afs. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-43463 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed6.19.10-1Update the kernel and reboot. Fixed in 6.19.10-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.19.10-1Update the kernel and reboot. Fixed in 6.19.10-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

rxrpc_kernel_lookup_peer() can also return error pointers in addition to NULL, so just checking for NULL is not sufficient. Fix this by: (1) Changing rxrpc_kernel_lookup_peer() to return -ENOMEM rather than NULL on allocation failure. (2) Making the callers in afs use IS_ERR() and PTR_ERR() to pass on the error code returned.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

fs/afs/addr_list.c
net/rxrpc/af_rxrpc.c

What this is
AFS FILESYSTEMMAINTAINERS section matched on fs/afs/ · linux-afs@lists.infradead.org · Supported
Kernel module
kafs

Check it on the machine

grep -w CONFIG_AFS_FS /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w kafs

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

  • bookworm, trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
M
a module where it is built at all; some flavours do not build it
Build switch
CONFIG_AFS_FS

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-05-08 (5 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.16%, higher than 4.8% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
fs/afs

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.86.18.19d55fa7cd4b19
6.86.19.954331c5dcc6d
6.87.04245a79003ad
6.7.300

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-43463, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.