-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] linux-azure kernel segfault in netfs module, netfs_rreq_unlock causes kernel panic on nodes #4726
Comments
Wrong image, was using AKSUbuntu-2204gen2containerd-202410.09.0 and earlier at the time of these incidents, updated information in bug report. |
Just confirmed the same segfault this past weekend, which does make sense because the kernel wasn't patched in 202412.10.0 . Full segfault below. It's safe to assume this will continue to happen until the kernel is patched or a different version is used for aks' images.
|
Describe the bug
This is a segmentation fault which exists in the netfs module of the linux-azure kernel (5.15.0-1075-azure). This was fixed in a later version, but not patched in the current AKS vm image. We've observed it on nodes with the cephfs module loaded.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Correct handling of XA_RETRY_ENTRY so that address 0000000000000402 is not dereferenced.
via https://github.com/torvalds/linux/blob/v5.15/fs/netfs/read_helper.c#L406 : On or after the first iteration of netfs_rreq_unlock,
page
can have the value XA_RETRY_ENTRY (returned by xas_find() in xas_for_each), which needs to be properly handled.Screenshots
6.8.0-1018-azure/kernel/fs/netfs/netfs.ko (correct handling of signal, taken from another VM, non-AKS):
5.15.0-1075-azure/kernel/fs/netfs/netfs.ko (segfault exists):
Environment:
Additional context
https://ubuntu.com/security/CVE-2023-52582
https://access.redhat.com/solutions/6993035
torvalds/linux@7e043a8
The text was updated successfully, but these errors were encountered: