Panel Discussion: What is Lacking in Linux Security and What Are or Should We be Doing about This
summary
Panel lays out concrete gaps and fixes: too few tests and regression suites, reliance on continuous fuzzing (syzkaller) but no oracle to mark security‑relevant crashes, and missing integration of C reproducers/Cs? into CI. Workable tools mentioned: Kconfig harden-check and LKDTM/KUnit/kernel self-tests; proposals include focused syscall fuzzers that reproduce known exploits, shipping file signatures in packages for provenance, and more resources for stable tree backports and hardware (TPM) testbeds. Watch if you want practical tool discussion and specific next steps.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:05Security Aspects in Linux Kernel Development Process
- 7:05Responsible Disclosure Procedure for Kernel Security Issues
- 8:01Kernel Security Technologies
- 22:32Main Reason for Very Large Number of Bugs in every Kernel Release and What Should Be Done Change To Reduce the Number of Bugs
- 27:26Problem with Static Code Analysis
- 42:52Testing the Kernel
- 59:01User Space Security
related talks
06mQ&A
27mSecurity: The Thing That Everyone...
32mEmbedded Linux Security: Dr Jekyll and Mr Hyde
06mLightning Talk: Security Down to the Kernel
46mThe State of Kernel Self Protection Project
21mFrom CVEs To Compliance: Automating Embedded Linux Kernel Security
45mLooking at Linux as a SEooC
59mGetting Started with Embedded Linux Security