Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release kernel-6.12.0-231.20.el10nv ALSA-2026:72059

Open
#3,676 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
linux

Research direction

This is a kernel security-release notice covering CVE-2025-39964, CVE-2026-53266, and CVE-2026-74581, with affected packages listed in the issue. Start by reviewing the CVE details and the NVIDIA for AlmaLinux 10 Release Notes referenced by the report. No contribution scope or completion criteria are specified, so the intended work must be clarified first.

Written by the indexing model from the issue text.

Description

kernel security update
Severity: Critical
Description
The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

  • kernel: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (CVE-2025-39964)
  • kernel: netfilter: ebtables SNAT target writes to shared memory pages during ARP hardware address rewrite (CVE-2026-53266)
  • kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res->rt6 pointer (CVE-2026-74581)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Additional Changes:

For detailed information on changes in this release, see the NVIDIA for AlmaLinux 10 Release Notes linked from the References section.

Affected packages:
kernel-6.12.0-231.20.el10nv.aarch64
kernel-64k-6.12.0-231.20.el10nv.aarch64
kernel-64k-core-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-core-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-devel-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-devel-matched-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-modules-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-modules-core-6.12.0-231.20.el10nv.aarch64
kernel-64k-debug-modules-extra-6.12.0-231.20.el10nv.aarch64
kernel-64k-devel-6.12.0-231.20.el10nv.aarch64
kernel-64k-devel-matched-6.12.0-231.20.el10nv.aarch64
kernel-64k-modules-6.12.0-231.20.el10nv.aarch64
kernel-64k-modules-core-6.12.0-231.20.el10nv.aarch64
kernel-64k-modules-extra-6.12.0-231.20.el10nv.aarch64
kernel-abi-stablelists-6.12.0-231.20.el10nv.noarch
kernel-core-6.12.0-231.20.el10nv.aarch64
kernel-cross-headers-6.12.0-231.20.el10nv.aarch64
kernel-debug-6.12.0-231.20.el10nv.aarch64
kernel-debug-core-6.12.0-231.20.el10nv.aarch64
kernel-debug-devel-6.12.0-231.20.el10nv.aarch64
kernel-debug-devel-matched-6.12.0-231.20.el10nv.aarch64
kernel-debug-modules-6.12.0-231.20.el10nv.aarch64
kernel-debug-modules-core-6.12.0-231.20.el10nv.aarch64
kernel-debug-modules-extra-6.12.0-231.20.el10nv.aarch64
kernel-devel-6.12.0-231.20.el10nv.aarch64
kernel-devel-matched-6.12.0-231.20.el10nv.aarch64
kernel-doc-6.12.0-231.20.el10nv.noarch
kernel-headers-6.12.0-231.20.el10nv.aarch64
kernel-modules-6.12.0-231.20.el10nv.aarch64
kernel-modules-core-6.12.0-231.20.el10nv.aarch64
kernel-modules-extra-6.12.0-231.20.el10nv.aarch64
kernel-modules-extra-matched-6.12.0-231.20.el10nv.aarch64
kernel-tools-6.12.0-231.20.el10nv.aarch64
kernel-tools-libs-6.12.0-231.20.el10nv.aarch64
kernel-tools-libs-devel-6.12.0-231.20.el10nv.aarch64
kernel-uki-virt-6.12.0-231.20.el10nv.aarch64
kernel-uki-virt-addons-6.12.0-231.20.el10nv.aarch64
libperf-6.12.0-231.20.el10nv.aarch64
perf-6.12.0-231.20.el10nv.aarch64
python3-perf-6.12.0-231.20.el10nv.aarch64
rtla-6.12.0-231.20.el10nv.aarch64
rv-6.12.0-231.20.el10nv.aarch64
kernel-abi-stablelists-6.12.0-231.20.el10nv.noarch
kernel-doc-6.12.0-231.20.el10nv.noarch

Dominant language
No language data
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AlmaLinux/updates

All issues in AlmaLinux/updates

Similar issues

More Operating Systems issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.