BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] With AI, 2, 000 Vulnerabilities per Linux kernel release
- Subject: [Discuss] With AI, 2, 000 Vulnerabilities per Linux kernel release
- From: kentborg at borg.org (Kent Borg)
- Date: Thu, 3 Sep 2026 20:55:35 -0700
- In-reply-to: <8f8940a4-6ef8-435f-85b4-684834f8b4b4@app.fastmail.com>
- References: <3ba75ddf-6d93-40c7-85ca-050531c8a4dd@app.fastmail.com> <121cb616-ba15-460b-8633-68b12007d2c1@borg.org> <20260411125347.7a3b1c48.Richard.Pieri@gmail.com> <aae1dbf0-dec1-46cb-b09c-82a6d0257b91@borg.org> <20260411191138.5e292aa7.Richard.Pieri@gmail.com> <cfbaecd3-841d-40d7-b7c1-b46c2200d5b7@borg.org> <20260411214838.56b593e0.Richard.Pieri@gmail.com> <mhAY9OfKywiwe5p9jbuWP4ZxR5fGgd7_uUqrqbjEws0md5d1BH7updt-DQ7IxVGAWZtMxIQEMFd_TyLwwGLDReULVRqU4GGGU_jnvKXUZOM=@cryptnet.net> <qh5h3x3w2kbe5voii3hcgo2vuapoxl7nrlvzgoug4nrsv2kr3v@mhmssfwu7rvo> <mFlzau6ezeaBP0gH7cGlxjM-oRrpyUc8glznQi72OZNepcPt-wIa5as8gnoeLwP9aUw6MPrmh3P8vutoMlhGvYQFdX4McXm4LKkiiX3RFoI=@cryptnet.net> <20260417142530.5ba22435.Richard.Pieri@gmail.com> <8f8940a4-6ef8-435f-85b4-684834f8b4b4@app.fastmail.com>
Companies that have really terrible security breaches?mostly don't get punished. After a few weeks of bad publicity the stock of publicly traded companies tends to go right back to where is was, like nothing every happened. We don't care about security because it is a waste of money. Exasperating! There is a major security problem that dates back over a half-century: When C was designed they were all clever and decided to make pointers and arrays and strings all kind of the same. People objected at the time, but we were assured that "we'll be careful, we're not idiots". There /is/ something that we really haven't tried: Building secure systems from the start. But that is also a money losing proposition. We worship "feature velocity" and actually stopping to decide what to build and maybe even design it? No way, that would sow things down and be too expensive. This evening I see there is an "urgency=high" update to Chromium for my machine. A whole lot of use-after-free and uninitialized-data and buffer-overflow and out-of-bounds bugs that weren't supposed to happen in C, because we promised we would be careful. Grrr. I will note that there are also a lot lines that read "drop, no longer needed with newer rust"! Rust is a full-featured language, so one can write bugs in Rust, too. But a whole lot of bugs will not be in code that the compiler is happy with. And Google has spent enough time rewriting Chromium in Rust and they have been doing it long enough, that they are already rolling out lots of Rust changes for things that are no longer needed. I will also note that the Linux kernel now has Rust, which is particularly valuable for device drivers. As with application code where, if it compiles it frequently just works, authors of Linux drivers are also noticing that if it compiles it frequently just works. For kernel drivers! Rust adoption is moving along well, and for new projects it is frequently the best choice. Security is a big reason. -kb
- References:
- [Discuss] With AI, 2,000 Vulnerabilities per Linux kernel release
- From: rrose at pobox.com (Randall Rose)
- [Discuss] With AI, 2,000 Vulnerabilities per Linux kernel release
- Prev by Date: [Discuss] With AI, 2, 000 Vulnerabilities per Linux kernel release
- Next by Date: [Discuss] With AI, 2, 000 Vulnerabilities per Linux kernel release
- Previous by thread: [Discuss] With AI, 2, 000 Vulnerabilities per Linux kernel release
- Next by thread: [Discuss] Linux command-line mystery: why does "cd" hang?
- Index(es):
