ZeroHour
oss-securitypublished ()ingested
Part of a story covered by 10 sources: “Four aged Linux kernel local root flaws (DirtyAH6, TUNderflow, PPPoEject, DiagSpill) disclosed with public exploits; fixes in stable kernels 5.10.270–7.2.4” — merged summary and timeline →

Re: A quartet of Linux local root vulns: DirtyAH6, PPPoEject, TUNderflow, and DiagSpill

mediumVulnerabilityimportance 45
AI summary · glm-5.3-flash

oss-security thread proposes hashing sorted Module.symvers CRCs under CONFIG_MODVERSIONS to fix four Linux local root vulnerabilities without breaking module ABI.

A follow-up post on oss-security discusses remediation for four Linux local root vulnerabilities dubbed DirtyAH6, PPPoEject, TUNderflow, and DiagSpill. The author argues no new package manager features are needed, and that loose version matching plus local source rebuilds create real ABI breakage risk. The proposal is to hash a sorted version of CRCs from Module.symvers whenever CONFIG_MODVERSIONS is enabled, avoiding reliance on brittle text-based version strings.

  • Thread covers fixes for four Linux local root flaws: DirtyAH6, PPPoEject, TUNderflow, DiagSpill
  • Author says no new package manager features are needed for the fix
  • Proposes hashing sorted Module.symvers CRCs when CONFIG_MODVERSIONS is enabled
  • Warns loose version matching and local source rebuilds can break kernel module ABI
Full article

Posted by Greg Dahlman on Sep 19 I may be missing something but I do see a path that may be clean without inventing new package manager features or relying on brittle, text-based version strings. The concern regarding loose version matching and local source rebuilds breaking the ABI is real, but IMHO we don't need to invent a new package manager feature to fix it. As long as `CONFIG_MODVERSIONS` is enabled, why not simply hash a sorted version of CRCs Module.symvers,...

This source does not provide full text. Read it at seclists.org.