The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete() so any code past that point risks touching already freed data. Try to avoid the locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend solely on the atomic ref counter for synchronization.
Kernel security advisory: https://lore.kernel.org/linux-cve-announce/2024022146-traction-unjustly-f451@gregkh/T/#u Upstream fix: https://github.com/torvalds/linux/commit/aec7961916f3
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2265535]
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:2394 https://access.redhat.com/errata/RHSA-2024:2394
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:4211 https://access.redhat.com/errata/RHSA-2024:4211
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:4352 https://access.redhat.com/errata/RHSA-2024:4352
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2024:4447 https://access.redhat.com/errata/RHSA-2024:4447
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:4533 https://access.redhat.com/errata/RHSA-2024:4533
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2024:5255 https://access.redhat.com/errata/RHSA-2024:5255