Back

HIGH

afs: Fix the setting of the server responding flag

Published Oct 21, 2024

Description

In afs_wait_for_operation(), we set transcribe the call responded flag to the server record that we used after doing the fileserver iteration loop - but it's possible to exit the loop having had a response from the server that we've discarded (e.g. it returned an abort or we started receiving data, but the call didn't complete).

This means that op->server might be NULL, but we don't check that before attempting to set the server flag.

Affected products

Remediation

Red Hat mitigation

To mitigate this issue, prevent the `afs` kernel module from loading. Create a file named `/etc/modprobe.d/disable-afs.conf` with the following content: `install afs /bin/true`. A system reboot is required for this change to take effect. This mitigation will prevent the use of the AFS filesystem.

References (9)

Change history (0)

No recorded changes yet.

Sources

CVE.org / MITRE

Status PUBLISHED
Assigner Linux
Published Oct 21, 2024
Updated Aug 5, 2026
Reserved Oct 21, 2024

CISA Vulnrichment

Updated Oct 22, 2024

NVD

Status Modified
Modified Aug 4, 2026

Red Hat

Severity Moderate
Public date Oct 21, 2024
Bugzilla 2320556

ENISA EUVD

Assigner Linux
Published Oct 21, 2024
Updated Aug 5, 2026

GitHub

No data