Thread

1. thallium205 · 1790900082 · focus · HN ↗

   Pretty much any kernel bug gets a CVE by default now, right?

   1. wjholden · 1790900405 · focus · HN ↗

      Is that all there is here? The quantifier "several" did not prepare me for the wall of CVE numbers in this list.

      1. vdfs · 1790902764 · focus · HN ↗

         <a href="https:&#x2F;&#x2F;docs.kernel.org&#x2F;process&#x2F;cve.html" rel="nofollow">https:&#x2F;&#x2F;docs.kernel.org&#x2F;process&#x2F;cve.html states that because almost any kernel bug can potentially compromise system security, the CVE team acts with extreme caution and labels nearly all bug fixes with a CVE
   2. slopinthebag · 1790901321 · focus · HN ↗

      yes because the majority are memory safety issues, and it&#x27;s automatically assumed that a memory safety bug can lead to a vuln

      one again illustrating the importance of encapsulating unsafe behavior. perhaps c should get a __UNSAFE { } block, where memory access is encapsulated and thus most bugs occurring outside of those blocks do not need to be marked as CVEs.

      1. akersten · 1790901610 · focus · HN ↗

         &gt; perhaps c should get a __UNSAFE { } block,

         I think the convention for this is at the filesystem level and most programmers use the `.c` suffix to indicate it

         1. slopinthebag · 1790902624 · focus · HN ↗

            in that case we need a block of system memory marked as unsafe so i can run these programs in it encapsulated

            perhaps we could call it a sedimentchest?

            1. catlifeonmars · 1790906148 · focus · HN ↗

               I think that’s just called “memory”. Encapsulation is your machine.
            2. someonebaggy · 1790914083 · focus · HN ↗

               See xkcd&#x27;s sandboxing cycle. They exist, they&#x27;re called processes
         2. branc116 · 1790930355 · focus · HN ↗

            cheap shot lol
      2. insanitybit · 1790915566 · focus · HN ↗

         No. It&#x27;s because Greg doesn&#x27;t like the CVE system and MITRE, the stupidest decision ever, made Greg a CNA, and this is his tantrum that he&#x27;s been waiting 40 years to throw.
      3. debugnik · 1790922904 · focus · HN ↗

         C has many more ways to trigger undefined behaviour than memory access. If C had unsafe blocks they&#x27;d restrict most forms of signed integer arithmetic and shifting, for a start.
   3. seba_dos1 · 1790902247 · focus · HN ↗

      Yes. It looks funny, but it&#x27;s a nothing burger.

Unofficial Hacker News client; not affiliated with Y Combinator.