41–50 of 152 posts
[flagged]
Obviously the way to prevent this is by bounds checking, which is literally in the `770594e` patch. It's just a bug and they happen routinely in all languages. Since this is doing pointer arithmetic, it could just as easily happen in unsafe Rust, for example.
Earlier quoted context omitted.
Like they said, "no way to prevent this" (kind of bug from happening again).
Static analysis and other tools can find this, but they're expensive; wonder what the kernel team has access to?
Also nice the onion reference by op.
Earlier quoted context omitted.
Static analysis and other tools can find this, but they're expensive; wonder what the kernel team has access to?
If not static analysis what would ai tools be considered? They're operating off the same source code Also nice the onion reference by op.
CAP_NET/SYS_ADMIN is required for this. So this would be "not as bad" as the others.
Earlier quoted context omitted.
Static analysis and other tools can find this, but they're expensive; wonder what the kernel team has access to?
If not static analysis what would ai tools be considered? They're operating off the same source code Also nice the onion reference by op.
[flagged]
Obviously the way to prevent this is by bounds checking, which is literally in the `770594e` patch. It's just a bug and they happen routinely in all languages. Since this is doing pointer arithmetic, it could just as easily happen in unsafe Rust, for example.
Earlier quoted context omitted.
Obviously the way to prevent this is by bounds checking, which is literally in the `770594e` patch. It's just a bug and they happen routinely in all languages. Since this is doing pointer arithmetic, it could just as easily happen in unsafe Rust, for example.
But one would have to explicitly choose to use unsafe Rust for this instead of ordinary safe Rust. And safe Rust has no particular difficulty writing to slots in an array or slice or vector specified by their index.
What is happening? I see multiple outages and CVEs is being reported on HN's front page. I've never seen these many security/incident related posts on HN's front page.
Automated vulnerability discovery via LLM.
[flagged]
Obviously the way to prevent this is by bounds checking, which is literally in the `770594e` patch. It's just a bug and they happen routinely in all languages. Since this is doing pointer arithmetic, it could just as easily happen in unsafe Rust, for example.