{"version":"2.1.323","anchor":"sandbox-denies-reads-of-prockcore-and-procvmcore","canonical_anchor":"sandbox-denies-reads-of-prockcore-and-procvmcore","heading":"Two more kernel memory files are blocked from being read","tier":"notice","area":"File Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sandbox-denies-reads-of-prockcore-and-procvmcore","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Two more kernel memory files are blocked from being read\n\nClaude Code now blocks \/proc\/kcore and \/proc\/vmcore along with \/proc\/kmsg in its list of special files\n\n**Unclear.** It is not clear whether this list is applied by the sandbox or by a separate read blocklist.\n\n**What**\n\nClaude Code keeps a list of special system files it blocks. On Linux it already held `\/proc\/kmsg`. It now also holds:\n\n- `\/proc\/kcore`\n\n- `\/proc\/vmcore`\n\nThese files expose images of the computer's kernel memory, the memory used by the core of the operating system.\n\n**Why**\n\nIt is a small step that stops tools from reading kernel memory images.\n\n- Area: File Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}