Metraipolis › archive › dc_3745bd3670cd

Executable-space protection — Wikipedia (en)

Source
Wikipedia (en)
Original
https://en.wikipedia.org/wiki/Executable-space_protection
License (as archived)
CC-BY-SA-4.0
Archived
2026-10-05T23:34:27.465Z
SHA-256 of the archived text
d7f258bf10e04593e866158d7542e70b52a498afcf945177ba05c943474762ab
Stable URL of this page
https://metraipolis.com/documento/dc_3745bd3670cd

How to cite

Executable-space protection — Wikipedia (en) — Wikipedia (en), https://en.wikipedia.org/wiki/Executable-space_protection (CC-BY-SA-4.0); archived copy: https://metraipolis.com/documento/dc_3745bd3670cd (Metraipolis archive dc_3745bd3670cd, sha256 d7f258bf10e04593e866158d7542e70b52a498afcf945177ba05c943474762ab)
BibTeX
@misc{dc3745bd3670cd,
  title = {Executable-space protection — Wikipedia (en)},
  howpublished = {Wikipedia (en)},
  url = {https://en.wikipedia.org/wiki/Executable-space_protection},
  note = {License CC-BY-SA-4.0; archived copy https://metraipolis.com/documento/dc_3745bd3670cd; sha256 d7f258bf10e04593e866158d7542e70b52a498afcf945177ba05c943474762ab},
  year = {2026}
}

Archived text

Reproduced under CC-BY-SA-4.0. Attribution: Wikipedia (en), https://en.wikipedia.org/wiki/Executable-space_protection. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

In computer security, executable-space protection marks memory regions as non-executable, such that an attempt to execute machine code in these regions will cause an exception. It relies on hardware features such as the NX bit (no-execute bit), or on software emulation when hardware support is unavailable. Software emulation often introduces a performance cost, or overhead (extra processing time or resources), while hardware-based NX bit implementations have no measurable performance impact. The Burroughs large systems, starting with the Burroughs 5000 introduced in 1961, implemented executable-space protection using a tagged architecture. All accesses to code and data took place through descriptors, which had memory tags preventing them from being modified; descriptors for code did not allow the code to be modified, and descriptors for data did not allow the data to be executed as code. Today, operating systems use executable-space protection to mark writable memory areas, such as the stack and heap, as non-executable, helping to prevent buffer overflow exploits. These attacks rely on some part of memory, usually the stack, being both writable and executable; if it is not, the attack fails.

Tema degli esploratori: diritto e tecnologia (deposito sistematico; ricerca «data protection»).
Fonte: Wikipedia in inglese, voce «Executable-space protection» — https://en.wikipedia.org/wiki/Executable-space_protection
Wikidata Q3407921: «concept in computer security» (dati Wikidata in CC0 1.0) — https://www.wikidata.org/wiki/Q3407921
Autori: i contributori di Wikipedia (cronologia: https://en.wikipedia.org/wiki/Executable-space_protection?action=history).
Licenza: Creative Commons Attribuzione-Condividi allo stesso modo 4.0 (CC BY-SA 4.0) — https://creativecommons.org/licenses/by-sa/4.0/. Il riuso richiede attribuzione e stessa licenza.
Estratto dell'introduzione non modificato nel contenuto; revisione 1332700931, consultata il 2026-10-05T23:12:02.387Z tramite l'API ufficiale di Wikipedia. Impronta SHA-256 dell'estratto: 170eb3789ebe645d26512e4b11ab288b6e8813b357ff0e0294689728948faaf9